[HDDS-3542] ozone chunkinfo CLI cannot connect to OM when run from NON OM leader client node

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 1.0.0
• Labels: TriagePending pull-request-available
• Target Version/s: 1.1.0
• Assignee: Sadanand Shenoy
• Reporter: Sadanand Shenoy
• Created: 05/May/20 05:58
• Updated: 06/Jan/25 14:12
• Resolved: 03/Jun/20 07:06

Description

When ozone debug chunkinfo command is run from a client node where OM leader is not present, the operation fails.
When run from the client node where OM leader is present, it works fine

/opt/cloudera/parcels/CDH/bin/ozone debug chunkinfo o3://ozone1/vol1/buck1/file1 20/04/21 11:04:02 INFO ipc.Client: Retrying connect to server: 0.0.0.0/0.0.0.0:9862. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=50, sleepTime=1000 MILLISECONDS) 20/04/21 11:04:03 INFO ipc.Client: Retrying connect to server: 0.0.0.0/0.0.0.0:9862. Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=50, sleepTime=1000 MILLISECONDS) 20/04/21 11:04:04 INFO ipc.Client: Retrying connect to server: 0.0.0.0/0.0.0.0:9862. Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=50, sleepTime=1000 MILLISECONDS) 20/04/21 11:04:05 INFO ipc.Client: Retrying connect to server: 0.0.0.0/0.0.0.0:9862. Already tried 3 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=50, sleepTime=1000 MILLISECONDS) 20/04/21 11:04:06 INFO ipc.Client: Retrying connect to server: 0.0.0.0/0.0.0.0:9862. Already tried 4 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=50, sleepTime=1000 MILLISECONDS)

Issue Links

• links to: GitHub Pull Request #993