Hi all,
I would like to discuss https://issues.apache.org/jira/browse/HDDS-6634 
<https://issues.apache.org/jira/browse/HDDS-6634>.
During our internal Ozone testing, we noticed that a datanode can be connected 
to another cluster (not the one the datanode had been initialized with). 
Although the conditions needed for issue reproduction are rather special (new 
SCM must have the same IP as the old one), theoretically there might be cases 
(like DNS spoofing) to hit it in a production environment. The idea of SCM 
processing another cluster's datanode reports seems catastrophic to me.

Reply via email to