We have Hortonworks cluster running on Linux platform. On the secondary Name node, the timeline and app history services often in stopped with maintenance mode on or started with maintenance mode on. Its Active-Standby (High Availability) node.
Is that a normal behavior? On secondary Name node in active-stand by architecture, it is normal to for the two services to be in stopped with maintenance mode on or started with maintenance mode on?
I used the cloudera distribution in the past, but on CDH distribution both Timeline and App History services were always running on both the active and standby nodes.
@Sandeep, thanks for the response. Is it normal or Architecture on the HDP cluster for these two services running only on Active Name node and not on the secondary name node?