You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by GitBox <gi...@apache.org> on 2019/10/24 22:29:23 UTC
[GitHub] [hadoop-ozone] smengcl commented on issue #9: HDDS-2240. Command
line tool for OM Admin
smengcl commented on issue #9: HDDS-2240. Command line tool for OM Admin
URL: https://github.com/apache/hadoop-ozone/pull/9#issuecomment-546128373
1. Compilation passed with `mvn clean install -DskipTests=true -Dmaven.javadoc.skip=true`
2. Checked `./hadoop-ozone/dist/target/ozone-0.5.0-SNAPSHOT/bin/ozone`, `admin` command shows up:
```
Client Commands:
admin Ozone admin tool
```
3. Ran `ozone admin om getserviceroles --om-service-id=id1` in a `docker-compose` cluster with profile `compose/ozone-om-ha/`. It succeeded on `om1` but throws this scary `protobuf.ServiceException`:
```
bash-4.2$ ozone admin om getserviceroles --om-service-id=id1
com.google.protobuf.ServiceException: org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.ozone.om.exceptions.NotLeaderException): OM om2 is not the leader. Suggested leader is om3
at org.apache.hadoop.ozone.protocolPB.OzoneManagerProtocolServerSideTranslatorPB.createNotLeaderException(OzoneManagerProtocolServerSideTranslatorPB.java:192)
at org.apache.hadoop.ozone.protocolPB.OzoneManagerProtocolServerSideTranslatorPB.submitReadRequestToOM(OzoneManagerProtocolServerSideTranslatorPB.java:178)
at org.apache.hadoop.ozone.protocolPB.OzoneManagerProtocolServerSideTranslatorPB.processRequest(OzoneManagerProtocolServerSideTranslatorPB.java:110)
at org.apache.hadoop.hdds.server.OzoneProtocolMessageDispatcher.processRequest(OzoneProtocolMessageDispatcher.java:72)
at org.apache.hadoop.ozone.protocolPB.OzoneManagerProtocolServerSideTranslatorPB.submitRequest(OzoneManagerProtocolServerSideTranslatorPB.java:100)
at org.apache.hadoop.ozone.protocol.proto.OzoneManagerProtocolProtos$OzoneManagerService$2.callBlockingMethod(OzoneManagerProtocolProtos.java)
at org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:524)
at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:1025)
at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:876)
at org.apache.hadoop.ipc.Server$RpcCall.run(Server.java:822)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.base/javax.security.auth.Subject.doAs(Subject.java:423)
at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1730)
at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2682)
, while invoking $Proxy16.submitRequest over nodeId=om2,nodeAddress=om2:9862 after 1 failover attempts. Trying to failover immediately.
om1 : FOLLOWER
om2 : FOLLOWER
om3 : LEADER
```
The same exception shows up when I'm running the same command on `om2` or `om3`. Looks like it is always trying to contact `om2`, which is not the leader in our case. Can we suppress this fail over message unless the command fails?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org