Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 09-18-2018 03:43 AM
What stores clusterID, namespaceID, and blockpoolID?
As far as I know...
${dfs.namenode.name.dir}/current/VERSION stores clusterID, namespaceID, and blockpoolID.
${dfs.journalnode.edits.dir}/${nameservice}/current/VERSION stores clusterID and namespaceID.
${dfs.datanode.data.dir}/current/VERSION stores clusterID.
Directory name under ${dfs.datanode.data.dir}/current includes blockpoolID.
${dfs.datanode.data.dir}/current/${blockpoolID}/current/VERSION stores namespaceID and blockpoolID.
Is there any other file or file name/directory name storing those IDs?
Created 09-19-2018 08:57 AM
The file/directory you mentioned are correct, apart from that i don't think there is any other location/file which has this information. Ref: https://hortonworks.com/blog/hdfs-metadata-directories-explained/
Created 09-19-2018 08:57 AM
The file/directory you mentioned are correct, apart from that i don't think there is any other location/file which has this information. Ref: https://hortonworks.com/blog/hdfs-metadata-directories-explained/
Created 09-19-2018 10:14 AM
Thanks, @Sandeep Nemuri
That reference link is also helpful!
Created 04-28-2020 12:25 AM
Hi,
I have a question regarding Cluster version.
There are separate nodes for primary and secondary machines, so the cluster version will be same or unique in this scenario?