Reply
New Contributor
Posts: 2
Registered: ‎09-07-2017

When is an hdfs-* service restart required?

A seemingly simple question, to which I can't find a clear answer.

 

Which services/node-types must be restarted for each of the configuration properties? For example, if I update the 'dfs.datanode.handler.count' property in the `hdfs-site.xml` configuration file, which services must be restarted? Can I get away with only restarting `datanodes`, or do I also need to restart `journalnodes` and/or `namenodes`, `zkfc` etc.

 

Just looking for clarification on this issue, though it seems that generally the advice is "restart everything"?

Champion
Posts: 597
Registered: ‎05-16-2016

Re: When is an hdfs-* service restart required?

Are you managing your cluster using cloudera manager ? 

New Contributor
Posts: 2
Registered: ‎09-07-2017

Re: When is an hdfs-* service restart required?

No, manually managed.

Highlighted
Champion
Posts: 597
Registered: ‎05-16-2016

Re: When is an hdfs-* service restart required?

[ Edited ]

since hdfs-site xml contains information / setting about hdfs daemons it is always good to restart namenode datanode and  secondaryname. 

In you case since you are only chaning the dfs.datanode.handler.count which at the datanode level you can just restart datanode alone . Hope this is suffice .

 

Announcements