[
https://issues.apache.org/jira/browse/HDDS-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16914169#comment-16914169
]
Elek, Marton commented on HDDS-2003:
------------------------------------
Works for me as well. Tested now.
Can be a synchronization issue, if the om is not running when the s3g is
starting up, it can be problematic.
I checked the starter script:
https://github.com/apache/hadoop-docker-ozone/blob/ozone-latest/start-ozone-all.sh
{code}
ozone scm --init
ozone scm &
ozone datanode &
#wait for scm startup
export WAITFOR=localhost:9876
/opt/starter.sh ozone om --init
/opt/starter.sh ozone om &
sleep 15
/opt/starter.sh ozone s3g
{code}
While it's not the best one, the 15 sleep time should be enough to start om.
You may executed the create-bucket command too early. Is it possible?
> Ozone - Easy simple start does not work as expected.
> ----------------------------------------------------
>
> Key: HDDS-2003
> URL: https://issues.apache.org/jira/browse/HDDS-2003
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: S3
> Affects Versions: 0.5.0
> Reporter: Anu Engineer
> Priority: Blocker
>
> During the verification of Ozone documentation, I followed the instructions
> on the easy start page.
>
> Run this instruction:
> {noformat}
> docker run -p 9878:9878 -p 9876:9876 apache/ozone {noformat}
> Followed by this command in another window:
> {noformat}
> aws s3api --endpoint http://localhost:9878/ create-bucket
> --bucket=bucket1{noformat}
>
> The S3Gateway is probably crashing since it is not able to find Ozone client.
> This is on trunk, I will reverify on the Ozone-0.4.1. FYI: [~elek],
> [~bharatviswa], [~nandakumar131].
>
> Here is the crash stack:
> {noformat}
> 2019-08-21 20:01:44 INFO SCMChillModeManager:274 - SCM in chill mode. 1
> DataNodes registered, 1 required.2019-08-21 20:01:44 INFO
> SCMChillModeManager:274 - SCM in chill mode. 1 DataNodes registered, 1
> required.2019-08-21 20:01:44 INFO SCMChillModeManager:110 - SCM exiting
> chill mode.2019-08-21 20:02:40 ERROR OzoneClientFactory:294 - 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:291)
> at
> org.apache.hadoop.ozone.client.OzoneClientFactory.getClient(OzoneClientFactory.java:92)
> at
> org.apache.hadoop.ozone.s3.OzoneClientProducer.createClient(OzoneClientProducer.java:45)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
