hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDDS-206) Ozone shell command doesn't respect KSM port set in ozone-site.xml
Date Mon, 02 Jul 2018 20:08:00 GMT

    [ https://issues.apache.org/jira/browse/HDDS-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16530387#comment-16530387
] 

Hudson commented on HDDS-206:
-----------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14513 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/14513/])
HDDS-206. Ozone shell command doesn't respect KSM port set in (nanda: rev ab2f8343a9810c9ec8b0920215a0897e7f671aba)
* (edit) hadoop-ozone/common/src/main/java/org/apache/hadoop/ozone/KsmUtils.java
* (edit) hadoop-ozone/client/src/main/java/org/apache/hadoop/ozone/client/OzoneClientFactory.java


> Ozone shell command doesn't respect KSM port set in ozone-site.xml
> ------------------------------------------------------------------
>
>                 Key: HDDS-206
>                 URL: https://issues.apache.org/jira/browse/HDDS-206
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone Manager
>            Reporter: Nilotpal Nandi
>            Assignee: Shashikant Banerjee
>            Priority: Major
>             Fix For: 0.2.1
>
>         Attachments: HDDS-206.00.patch, HDDS-206.01.patch
>
>
> Here is the output of ozone -listVolume command without any port mentioned .
> By default, it chooses the port number as 9862 which is not mentioned in the ozone-site.xml
> {noformat}
> [root@ozone-vm bin]# ./ozone oz -listVolume o3://127.0.0.1/
> 2018-06-29 04:42:20,652 WARN util.NativeCodeLoader: Unable to load native-hadoop library
for your platform... using builtin-java classes where applicable
> 2018-06-29 04:42:21,914 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:9862.
Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10,
sleepTime=1000 MILLISECONDS)
> 2018-06-29 04:42:22,915 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:9862.
Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10,
sleepTime=1000 MILLISECONDS)
> 2018-06-29 04:42:23,917 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:9862.
Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10,
sleepTime=1000 MILLISECONDS)
> 2018-06-29 04:42:24,925 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:9862.
Already tried 3 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10,
sleepTime=1000 MILLISECONDS)
> 2018-06-29 04:42:25,928 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:9862.
Already tried 4 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10,
sleepTime=1000 MILLISECONDS)
> 2018-06-29 04:42:26,931 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:9862.
Already tried 5 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10,
sleepTime=1000 MILLISECONDS)
> 2018-06-29 04:42:27,932 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:9862.
Already tried 6 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10,
sleepTime=1000 MILLISECONDS)
> 2018-06-29 04:42:28,934 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:9862.
Already tried 7 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10,
sleepTime=1000 MILLISECONDS)
> 2018-06-29 04:42:29,935 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:9862.
Already tried 8 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10,
sleepTime=1000 MILLISECONDS)
> 2018-06-29 04:42:30,938 INFO ipc.Client: Retrying connect to server: localhost/127.0.0.1:9862.
Already tried 9 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10,
sleepTime=1000 MILLISECONDS)
> 2018-06-29 04:42:31,075 [main] ERROR - Couldn't create protocol class org.apache.hadoop.ozone.client.rpc.RpcClient
exception:
> java.lang.reflect.InvocationTargetException
>  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>  at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>  at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>  at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>  at org.apache.hadoop.ozone.client.OzoneClientFactory.getClientProtocol(OzoneClientFactory.java:292)
>  at org.apache.hadoop.ozone.client.OzoneClientFactory.getRpcClient(OzoneClientFactory.java:172)
>  at org.apache.hadoop.ozone.client.OzoneClientFactory.getRpcClient(OzoneClientFactory.java:156)
>  at org.apache.hadoop.ozone.client.OzoneClientFactory.getRpcClient(OzoneClientFactory.java:111)
>  at org.apache.hadoop.ozone.web.ozShell.Handler.verifyURI(Handler.java:96)
>  at org.apache.hadoop.ozone.web.ozShell.volume.ListVolumeHandler.execute(ListVolumeHandler.java:80)
>  at org.apache.hadoop.ozone.web.ozShell.Shell.dispatch(Shell.java:395)
>  at org.apache.hadoop.ozone.web.ozShell.Shell.run(Shell.java:135)
>  at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
>  at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90)
>  at org.apache.hadoop.ozone.web.ozShell.Shell.main(Shell.java:114)
> Caused by: java.net.ConnectException: Call From ozone-vm/10.200.5.166 to localhost:9862
failed on connection exception: java.net.ConnectException: Connection refused; For more details
see: http://wiki.apache.org/hadoop/ConnectionRefused
>  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>  at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>  at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>  at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>  at org.apache.hadoop.net.NetUtils.wrapWithMessage(NetUtils.java:831)
>  at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:755)
>  at org.apache.hadoop.ipc.Client.getRpcResponse(Client.java:1503)
>  at org.apache.hadoop.ipc.Client.call(Client.java:1445)
>  at org.apache.hadoop.ipc.Client.call(Client.java:1355)
>  at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:228)
>  at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:116)
>  at com.sun.proxy.$Proxy6.getServiceList(Unknown Source)
>  at org.apache.hadoop.ozone.ksm.protocolPB.KeySpaceManagerProtocolClientSideTranslatorPB.getServiceList(KeySpaceManagerProtocolClientSideTranslatorPB.java:745)
>  at org.apache.hadoop.ozone.client.rpc.RpcClient.getScmAddressForClient(RpcClient.java:158)
>  at org.apache.hadoop.ozone.client.rpc.RpcClient.<init>(RpcClient.java:131)
>  ... 15 more
> Caused by: java.net.ConnectException: Connection refused
>  at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
>  at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
>  at org.apache.hadoop.net.SocketIOWithTimeout.connect(SocketIOWithTimeout.java:206)
>  at org.apache.hadoop.net.NetUtils.connect(NetUtils.java:531)
>  at org.apache.hadoop.ipc.Client$Connection.setupConnection(Client.java:686)
>  at org.apache.hadoop.ipc.Client$Connection.setupIOstreams(Client.java:789)
>  at org.apache.hadoop.ipc.Client$Connection.access$3600(Client.java:410)
>  at org.apache.hadoop.ipc.Client.getConnection(Client.java:1560)
>  at org.apache.hadoop.ipc.Client.call(Client.java:1391)
>  ... 22 more
> Command Failed : Call From ozone-vm/10.200.5.166 to localhost:9862 failed on connection
exception: java.net.ConnectException: Connection refused; For more details see: http://wiki.apache.org/hadoop/ConnectionRefused
> {noformat}
>  
> ozone-site.xml
> ------------------------
>  
> {noformat}
> [root@ozone-vm hadoop]# cat ozone-site.xml
> <?xml version="1.0" encoding="UTF-8"?>
> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
> <configuration>
>  <property>
>  <name>ozone.enabled</name>
>  <value>True</value>
>  </property>
> <property>
>  <name>ozone.metadata.dirs</name>
>  <value>/tmp/scm/meta</value>
>  </property>
> <property>
>  <name>ozone.scm.names</name>
>  <value>127.0.0.1</value>
>  </property>
> <property>
>  <name>ozone.scm.client.address</name>
>  <value>127.0.0.1:9860</value>
>  </property>
> <property>
>  <name>ozone.scm.block.client.address</name>
>  <value>127.0.0.1:9863</value>
>  </property>
> <property>
>  <name>ozone.scm.datanode.address</name>
>  <value>127.0.0.1:9861</value>
>  </property>
> <property>
>  <name>ozone.ksm.address</name>
>  <value>127.0.0.1:9884</value>
>  </property>
>  <property>
>  <name>dfs.container.ratis.enabled</name>
>  <value>false</value>
>  </property>
>  <property>
>  <name>ozone.replication</name>
>  <value>1</value>
>  </property>
> </configuration>
> {noformat}
>  
>  
> when run with the port number mentioned in ozone-site.xml , listVolume commands works
well :
>  
> {noformat}
> [root@ozone-vm bin]# ./ozone oz -listVolume o3://127.0.0.19884/
> 2018-06-29 04:50:47,979 WARN util.NativeCodeLoader: Unable to load native-hadoop library
for your platform... using builtin-java classes where applicable
> [ {
>  "owner" : {
>  "name" : "root"
>  },
>  "quota" : {
>  "unit" : "TB",
>  "size" : 1048576
>  },
>  "volumeName" : "nnvolume1",
>  "createdOn" : "Sun, 18 Sep +50444 15:12:11 GMT",
>  "createdBy" : "root"
> }, {
>  "owner" : {
>  "name" : "root"
>  },
>  "quota" : {
>  "unit" : "TB",
>  "size" : 1048576
>  },
>  "volumeName" : "nnvolume2",
>  "createdOn" : "Tue, 27 Sep +50444 13:05:43 GMT",
>  "createdBy" : "root"
> } ]
>  
> {noformat}
>  
> expectation :
> --------------------
>  # Default port number should not be taken as 9862.
>  # If port number is not mentioned for object manager, default value should be taken
from ozone-site.xml (in this case , it should be 9884)
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message