sokui commented on PR #3186: URL: https://github.com/apache/ozone/pull/3186#issuecomment-1140192065
> @sokui I have tweaked the test slightly in my fork to verify datanodes are functional after restart. > > (Note that I have removed the `ozone-dn-restart` environment, since it mostly duplicated the `ozone` environment. In Docker-based acceptance test we need two separate environments due to some Docker-specific behavior. But with Kubernetes I think we can merge them, and add the config property and tests in `ozone` instead. Please consider including this change in the PR.) > > There seems to be some problem If all three datanodes are restarted. Here are the logs (in `ozone` directory): https://github.com/adoroszlai/hadoop-ozone/suites/6617501193/artifacts/249176241 > > However, restarting only one datanode looks good: https://github.com/adoroszlai/hadoop-ozone/actions/runs/2371075415 Hi @adoroszlai , I checked your logs. Have you set this config? OZONE-SITE.XML_dfs.datanode.use.datanode.hostname: true. This will use datanode hostname as address for RATIS. It seems that your logs shows you are using datanode ip as RATIS address. Then when datanodes restart, I am not sure if the Ip changes, it will still work. Could you please test it with this setting again? Regarding with merging the restart test with ozone environment. How did you do that? Did you create another configmap2.yaml, and test-restart.sh for it? Please let me know. I can make the change accordingly. Thanks -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
