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 "Nilotpal Nandi (JIRA)" <ji...@apache.org> on 2019/03/29 11:49:00 UTC
[jira] [Resolved] (HDDS-1298) blockade tests failing as the nodes
are not able to communicate with Ozone Manager
[ https://issues.apache.org/jira/browse/HDDS-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nilotpal Nandi resolved HDDS-1298.
----------------------------------
Resolution: Duplicate
> blockade tests failing as the nodes are not able to communicate with Ozone Manager
> ----------------------------------------------------------------------------------
>
> Key: HDDS-1298
> URL: https://issues.apache.org/jira/browse/HDDS-1298
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Nilotpal Nandi
> Assignee: Nilotpal Nandi
> Priority: Critical
> Attachments: alllogs.log
>
>
> steps taken:
> --------------------
> # started 3 datanodes docker cluster.
> # freon run fails with error : "No such service: ozoneManager"
>
> {noformat}
> om_1 | STARTUP_MSG: build = https://github.com/apache/hadoop.git -r e97acb3bd8f3befd27418996fa5d4b50bf2e17bf; compiled by 'sunilg' on 2019-01-15T17:34Z
> om_1 | STARTUP_MSG: java = 11.0.1
> om_1 | ************************************************************/
> om_1 | 2019-03-18 06:31:41 INFO OzoneManager:51 - registered UNIX signal handlers for [TERM, HUP, INT]
> om_1 | 2019-03-18 06:31:41 WARN ScmUtils:77 - ozone.om.db.dirs is not configured. We recommend adding this setting. Falling back to ozone.metadata.dirs instead.
> om_1 | 2019-03-18 06:31:41 INFO OzoneManager:484 - OM Service ID is not set. Setting it to the default ID: omServiceIdDefault
> om_1 | 2019-03-18 06:31:41 INFO OzoneManager:490 - OM Node ID is not set. Setting it to the OmStorage's OmID: 25501758-f7f6-42d5-8196-52a885af7e23
> om_1 | 2019-03-18 06:31:41 INFO OzoneManager:441 - Found matching OM address with OMServiceId: null, OMNodeId: null, RPC Address: om:9862 and Ratis port: 9872
> om_1 | 2019-03-18 06:31:42 WARN ScmUtils:77 - ozone.om.db.dirs is not configured. We recommend adding this setting. Falling back to ozone.metadata.dirs instead.
> om_1 | 2019-03-18 06:31:42 INFO log:192 - Logging initialized @4061ms
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:101 - using custom profile for table: userTable
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:152 - Using default column profile:DBProfile.DISK for Table:userTable
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:101 - using custom profile for table: volumeTable
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:152 - Using default column profile:DBProfile.DISK for Table:volumeTable
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:101 - using custom profile for table: bucketTable
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:152 - Using default column profile:DBProfile.DISK for Table:bucketTable
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:101 - using custom profile for table: keyTable
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:152 - Using default column profile:DBProfile.DISK for Table:keyTable
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:101 - using custom profile for table: deletedTable
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:152 - Using default column profile:DBProfile.DISK for Table:deletedTable
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:101 - using custom profile for table: openKeyTable
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:152 - Using default column profile:DBProfile.DISK for Table:openKeyTable
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:101 - using custom profile for table: s3Table
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:152 - Using default column profile:DBProfile.DISK for Table:s3Table
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:101 - using custom profile for table: multipartInfoTable
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:152 - Using default column profile:DBProfile.DISK for Table:multipartInfoTable
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:101 - using custom profile for table: s3SecretTable
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:152 - Using default column profile:DBProfile.DISK for Table:s3SecretTable
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:101 - using custom profile for table: default
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:158 - Using default column profile:DBProfile.DISK for Table:default
> om_1 | 2019-03-18 06:31:42 INFO DBStoreBuilder:189 - Using default options. DBProfile.DISK
> om_1 | 2019-03-18 06:31:42 INFO CallQueueManager:84 - Using callQueue: class java.util.concurrent.LinkedBlockingQueue, queueCapacity: 2000, scheduler: class org.apache.hadoop.ipc.DefaultRpcScheduler, ipcBackoff: false.
> om_1 | 2019-03-18 06:31:42 INFO Server:1074 - Starting Socket Reader #1 for port 9862
> om_1 | 2019-03-18 06:31:43 WARN ScmUtils:77 - ozone.om.db.dirs is not configured. We recommend adding this setting. Falling back to ozone.metadata.dirs instead.
> om_1 | 2019-03-18 06:31:43 INFO OzoneManager:1129 - OzoneManager RPC server is listening at om/172.21.0.3:9862
> om_1 | 2019-03-18 06:31:43 INFO MetricsConfig:118 - Loaded properties from hadoop-metrics2.properties
> om_1 | 2019-03-18 06:31:43 INFO MetricsSystemImpl:374 - Scheduled Metric snapshot period at 10 second(s).
> om_1 | 2019-03-18 06:31:43 INFO MetricsSystemImpl:191 - OzoneManager metrics system started
> om_1 | 2019-03-18 06:31:43 INFO Server:1314 - IPC Server Responder: starting
> om_1 | 2019-03-18 06:31:43 INFO Server:1153 - IPC Server listener on 9862: starting
> om_1 | 2019-03-18 06:31:43 INFO DFSUtil:1641 - Starting Web-server for ozoneManager at: http://0.0.0.0:9874
> om_1 | 2019-03-18 06:31:43 INFO AuthenticationFilter:240 - Unable to initialize FileSignerSecretProvider, falling back to use random secrets.
> om_1 | 2019-03-18 06:31:43 INFO HttpRequestLog:81 - Http request log for http.requests.ozoneManager is not defined
> om_1 | 2019-03-18 06:31:43 INFO HttpServer2:975 - Added global filter 'safety' (class=org.apache.hadoop.http.HttpServer2$QuotingInputFilter)
> om_1 | 2019-03-18 06:31:43 INFO HttpServer2:948 - Added filter static_user_filter (class=org.apache.hadoop.http.lib.StaticUserWebFilter$StaticUserFilter) to context ozoneManager
> om_1 | 2019-03-18 06:31:43 INFO HttpServer2:958 - Added filter static_user_filter (class=org.apache.hadoop.http.lib.StaticUserWebFilter$StaticUserFilter) to context static
> om_1 | 2019-03-18 06:31:43 INFO HttpServer2:958 - Added filter static_user_filter (class=org.apache.hadoop.http.lib.StaticUserWebFilter$StaticUserFilter) to context logs
> om_1 | 2019-03-18 06:31:43 INFO HttpServer2:1191 - Jetty bound to port 9874
> om_1 | 2019-03-18 06:31:43 INFO Server:351 - jetty-9.3.24.v20180605, build timestamp: 2018-06-05T17:11:56Z, git hash: 84205aa28f11a4f31f2a3b86d1bba2cc8ab69827
> om_1 | 2019-03-18 06:31:43 INFO ContextHandler:781 - Started o.e.j.s.ServletContextHandler@620c8641{/logs,file:///opt/hadoop/logs/,AVAILABLE}
> om_1 | 2019-03-18 06:31:43 INFO ContextHandler:781 - Started o.e.j.s.ServletContextHandler@68d7a2df{/static,jar:file:/opt/hadoop/share/ozone/lib/hadoop-ozone-ozone-manager-0.5.0-SNAPSHOT.jar!/webapps/static,AVAILABLE}
> om_1 | 2019-03-18 06:31:43 INFO ContextHandler:781 - Started o.e.j.w.WebAppContext@57272109{/,file:///tmp/jetty-0.0.0.0-9874-ozoneManager-_-any-11206983497472345410.dir/webapp/,AVAILABLE}{/ozoneManager}
> om_1 | 2019-03-18 06:31:43 INFO AbstractConnector:278 - Started ServerConnector@2cc75074{HTTP/1.1,[http/1.1]}{0.0.0.0:9874}
> om_1 | 2019-03-18 06:31:43 INFO Server:419 - Started @5079ms
> om_1 | 2019-03-18 06:31:43 INFO BaseHttpServer:207 - HTTP server of OZONEMANAGER is listening at http://0.0.0.0:9874{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org