adoroszlai commented on PR #3186:
URL: https://github.com/apache/ozone/pull/3186#issuecomment-1141681402

   > Thanks for suggestion. I cherry-picked your commits.
   
   @sokui Thanks.
   
   Further checking the logs I realized that we also need to enable the FQDN 
enhancement from HDDS-5919, here's my change for that: 
https://github.com/adoroszlai/hadoop-ozone/commit/2af38161a
   
   But even with the above change, the test still fails.  It seems datanodes 
cannot communicate to elect leader for the new pipeline, e.g.:
   
   ```
   2022-05-31 04:41:12 INFO  LeaderElection:89 - 
3a7efa44-2676-4c59-a94a-57c379b16550@group-7288CA2A4B95-LeaderElection7: 
ELECTION REJECTED received 0 response(s) and 2 exception(s):
   2022-05-31 04:41:12 INFO  LeaderElection:137 -   Exception 0: 
java.util.concurrent.ExecutionException: 
org.apache.ratis.thirdparty.io.grpc.StatusRuntimeException: UNAVAILABLE: io 
exception
   2022-05-31 04:41:12 INFO  LeaderElection:137 -   Exception 1: 
java.util.concurrent.ExecutionException: 
org.apache.ratis.thirdparty.io.grpc.StatusRuntimeException: UNAVAILABLE: io 
exception
   ```
   
   > I see there are two test failures.
   > 1. TestRootedOzoneFileSystem. testRenameToTrashEnabled
   
   You can ignore this one for now, it is flaky.
   
   > 2. kubernetes/examples/ozone/test.sh
   
   Logs are available in the workflow run artifact, which is at the bottom of 
the workflow "Summary" page.
   
   https://github.com/adoroszlai/hadoop-ozone/actions/runs/2412586657#artifacts


-- 
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]

Reply via email to