Hi, Thanks for your answer. I've got one more question.
> > Are clusterid and nodeid something heketi uses only internally and are not > > directly connected to something within glusterfs? > Yes, in glusterd there is no concept of clusterid. It is an id that heketi > creates to refer to a particular cluster. > Nodeid: glusterd generates a node id for all peers in the cluster but the > nodeid in heketi topology info is "local" only to heketi as it has to create > the nodeid before the peer probe command. Does this mean that when I could change clusterid and nodeids in a heketi-topology file, reload it into heketi db and, as long as all references are fine within the topology file, all volumes and bricks should be safe? I'm asking because I'm thinking about writing a script to generate a heketi-topology out of a gluster with all volumes/bricks in a safe state to recreate a corrupted heketi.db file. Greetings, Johannes Internal
_______________________________________________ heketi-devel mailing list heketi-devel@gluster.org https://lists.gluster.org/mailman/listinfo/heketi-devel
