[
https://issues.apache.org/jira/browse/HDDS-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-3324:
---------------------------------
Labels: pull-request-available (was: )
> OM Client fails with StringIndexOutOfBoundsException
> ----------------------------------------------------
>
> Key: HDDS-3324
> URL: https://issues.apache.org/jira/browse/HDDS-3324
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Namit Maheshwari
> Assignee: Bharat Viswanadham
> Priority: Major
> Labels: pull-request-available
>
> OM Client fails with StringIndexOutOfBoundsException:
>
> {code:java}
> 2020-03-31T09:53:03,673 INFO [Thread-16] jdbc.TestDriver: Caused by:
> java.io.IOException: Couldn't create RpcClient protocol
> 2020-03-31T09:53:03,673 INFO [Thread-16] jdbc.TestDriver: at
> org.apache.hadoop.ozone.client.OzoneClientFactory.getClientProtocol(OzoneClientFactory.java:199)
> 2020-03-31T09:53:03,673 INFO [Thread-16] jdbc.TestDriver: at
> org.apache.hadoop.ozone.client.OzoneClientFactory.getClientProtocol(OzoneClientFactory.java:175)
> 2020-03-31T09:53:03,673 INFO [Thread-16] jdbc.TestDriver: at
> org.apache.hadoop.ozone.client.OzoneClientFactory.getRpcClient(OzoneClientFactory.java:86)
> 2020-03-31T09:53:03,673 INFO [Thread-16] jdbc.TestDriver: at
> org.apache.hadoop.fs.ozone.BasicOzoneClientAdapterImpl.<init>(BasicOzoneClientAdapterImpl.java:168)
> 2020-03-31T09:53:03,673 INFO [Thread-16] jdbc.TestDriver: at
> org.apache.hadoop.fs.ozone.OzoneClientAdapterImpl.<init>(OzoneClientAdapterImpl.java:50)
> 2020-03-31T09:53:03,674 INFO [Thread-16] jdbc.TestDriver: at
> org.apache.hadoop.fs.ozone.OzoneFileSystem.createAdapter(OzoneFileSystem.java:103)
> 2020-03-31T09:53:03,674 INFO [Thread-16] jdbc.TestDriver: at
> org.apache.hadoop.fs.ozone.BasicOzoneFileSystem.initialize(BasicOzoneFileSystem.java:158)
> 2020-03-31T09:53:03,674 INFO [Thread-16] jdbc.TestDriver: at
> org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:3391)
> 2020-03-31T09:53:03,674 INFO [Thread-16] jdbc.TestDriver: at
> org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:158)
> 2020-03-31T09:53:03,674 INFO [Thread-16] jdbc.TestDriver: at
> org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:3451)
> 2020-03-31T09:53:03,674 INFO [Thread-16] jdbc.TestDriver: at
> org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:3419)
> 2020-03-31T09:53:03,674 INFO [Thread-16] jdbc.TestDriver: at
> org.apache.hadoop.fs.FileSystem.get(FileSystem.java:513)
> 2020-03-31T09:53:03,674 INFO [Thread-16] jdbc.TestDriver: at
> org.apache.hadoop.fs.Path.getFileSystem(Path.java:361)
> 2020-03-31T09:53:03,674 INFO [Thread-16] jdbc.TestDriver: at
> org.apache.hadoop.hive.ql.exec.FileSinkOperator.initializeOp(FileSinkOperator.java:558)
> 2020-03-31T09:53:03,674 INFO [Thread-16] jdbc.TestDriver: ... 26 more
> 2020-03-31T09:53:03,674 INFO [Thread-16] jdbc.TestDriver: Caused by:
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> 2020-03-31T09:53:03,674 INFO [Thread-16] jdbc.TestDriver: at
> java.base/java.lang.String.substring(String.java:1841)
> 2020-03-31T09:53:03,674 INFO [Thread-16] jdbc.TestDriver: at
> org.apache.hadoop.ozone.om.ha.OMFailoverProxyProvider.computeDelegationTokenService(OMFailoverProxyProvider.java:207)
> 2020-03-31T09:53:03,674 INFO [Thread-16] jdbc.TestDriver: at
> org.apache.hadoop.ozone.om.ha.OMFailoverProxyProvider.<init>(OMFailoverProxyProvider.java:84)
> 2020-03-31T09:53:03,674 INFO [Thread-16] jdbc.TestDriver: at
> org.apache.hadoop.ozone.om.protocolPB.OzoneManagerProtocolClientSideTranslatorPB.<init>(OzoneManagerProtocolClientSideTranslatorPB.java:208)
> 2020-03-31T09:53:03,674 INFO [Thread-16] jdbc.TestDriver: at
> org.apache.hadoop.ozone.client.rpc.RpcClient.<init>(RpcClient.java:154)
> 2020-03-31T09:53:03,674 INFO [Thread-16] jdbc.TestDriver: at
> org.apache.hadoop.ozone.client.OzoneClientFactory.getClientProtocol(OzoneClientFactory.java:192)
> 2020-03-31T09:53:03,674 INFO [Thread-16] jdbc.TestDriver: ... 39 more
> {code}
>
> This can happen for two reasons:
> # If user has configured OM addresses incorrectly which are not resolvable
> to any host.
> # In Docker world when the client starts if all OM containers are down, then
> OM addresses will be unresolvable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
