You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@accumulo.apache.org by "Samudrala, Ranganath [USA] via user" <us...@accumulo.apache.org> on 2023/01/20 14:53:04 UTC

Exception during accumulo init

Hello

The setup is in Kubernetes and Accumulo version is v2.10. None of the accumulo processes are running. Hadoop services are running is separate pods.  I open a shell in the Accumulo manager/master pod and invoked the command “accumulo init –upload-accumulo-props” .  I see an exception in the log and I am wondering if this is normal/acceptable or this problem should be resolved before attempting perform a start?

ERROR StatusLogger An exception occurred processing Appender MonitorLog
java.lang.RuntimeException: Accumulo not initialized, there is no instance id at hdfs://accumulo-hdfs-namenode-0.accumulo-hdfs-namenodes:8020/accumulo/instance_id
                at org.apache.accumulo.server.fs.VolumeManager.getInstanceIDFromHdfs(VolumeManager.java:218)
                at org.apache.accumulo.server.ServerInfo.<init>(ServerInfo.java:102)
                at org.apache.accumulo.server.ServerContext.<init>(ServerContext.java:106)
                at org.apache.accumulo.monitor.util.logging.AccumuloMonitorAppender.lambda$new$1(AccumuloMonitorAppender.java:93)
                at org.apache.accumulo.monitor.util.logging.AccumuloMonitorAppender.append(AccumuloMonitorAppender.java:111)
                at org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:161)
                at org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:134)
                at org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:125)
                at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:89)
                at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:683)
                at org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:641)
                at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:624)
                at org.apache.logging.log4j.core.config.LoggerConfig.logParent(LoggerConfig.java:674)
                at org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:643)
                at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:624)
                at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:612)
                at org.apache.logging.log4j.core.config.AwaitCompletionReliabilityStrategy.log(AwaitCompletionReliabilityStrategy.java:98)
                at org.apache.logging.log4j.core.async.AsyncLogger.actualAsyncLog(AsyncLogger.java:488)
                at org.apache.logging.log4j.core.async.RingBufferLogEvent.execute(RingBufferLogEvent.java:156)
                at org.apache.logging.log4j.core.async.RingBufferLogEventHandler.onEvent(RingBufferLogEventHandler.java:51)
                at org.apache.logging.log4j.core.async.RingBufferLogEventHandler.onEvent(RingBufferLogEventHandler.java:29)
                at com.lmax.disruptor.BatchEventProcessor.processEvents(BatchEventProcessor.java:168)
                at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:125)
                at java.base/java.lang.Thread.run(Thread.java:829)

Thanks
Ranga

Re: Exception during accumulo init

Posted by "Samudrala, Ranganath [USA] via user" <us...@accumulo.apache.org>.
Is it a problem when the option “—upload-accumulo-props” is used? This is documented here: https://github.com/apache/accumulo-docker

I tried without that option, and the end result is the same.

Thanks
Ranga


From: dev1 <de...@etcoleman.com>
Date: Friday, January 20, 2023 at 11:05 AM
To: user@accumulo.apache.org <us...@accumulo.apache.org>, Samudrala, Ranganath [USA] <Sa...@bah.com>
Subject: [External] RE: Exception during accumulo init
Why do you keep using “—upload-accumulo-props~?  During initialization Accumulo will automatically read your site config file and then set properties in ZooKeeper accordingly.

Ed Coleman

From: Samudrala, Ranganath [USA] via user <us...@accumulo.apache.org>
Sent: Friday, January 20, 2023 10:48 AM
To: user@accumulo.apache.org
Subject: Re: Exception during accumulo init

I think this problem is resolved. Lower down in the log, after  I enter the credentials, I can see logs related to accumul/<instance_id>.

From: Samudrala, Ranganath [USA] via user <us...@accumulo.apache.org>>
Date: Friday, January 20, 2023 at 9:53 AM
To: Samudrala, Ranganath [USA] via user <us...@accumulo.apache.org>>
Subject: [External] Exception during accumulo init
Hello

The setup is in Kubernetes and Accumulo version is v2.10. None of the accumulo processes are running. Hadoop services are running is separate pods.  I open a shell in the Accumulo manager/master pod and invoked the command “accumulo init –upload-accumulo-props” .  I see an exception in the log and I am wondering if this is normal/acceptable or this problem should be resolved before attempting perform a start?

ERROR StatusLogger An exception occurred processing Appender MonitorLog
java.lang.RuntimeException: Accumulo not initialized, there is no instance id at hdfs://accumulo-hdfs-namenode-0.accumulo-hdfs-namenodes:8020/accumulo/instance_id
                at org.apache.accumulo.server.fs.VolumeManager.getInstanceIDFromHdfs(VolumeManager.java:218)
                at org.apache.accumulo.server.ServerInfo.<init>(ServerInfo.java:102)
                at org.apache.accumulo.server.ServerContext.<init>(ServerContext.java:106)
                at org.apache.accumulo.monitor.util.logging.AccumuloMonitorAppender.lambda$new$1(AccumuloMonitorAppender.java:93)
                at org.apache.accumulo.monitor.util.logging.AccumuloMonitorAppender.append(AccumuloMonitorAppender.java:111)
                at org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:161)
                at org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:134)
                at org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:125)
                at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:89)
                at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:683)
                at org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:641)
                at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:624)
                at org.apache.logging.log4j.core.config.LoggerConfig.logParent(LoggerConfig.java:674)
                at org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:643)
                at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:624)
                at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:612)
                at org.apache.logging.log4j.core.config.AwaitCompletionReliabilityStrategy.log(AwaitCompletionReliabilityStrategy.java:98)
                at org.apache.logging.log4j.core.async.AsyncLogger.actualAsyncLog(AsyncLogger.java:488)
                at org.apache.logging.log4j.core.async.RingBufferLogEvent.execute(RingBufferLogEvent.java:156)
                at org.apache.logging.log4j.core.async.RingBufferLogEventHandler.onEvent(RingBufferLogEventHandler.java:51)
                at org.apache.logging.log4j.core.async.RingBufferLogEventHandler.onEvent(RingBufferLogEventHandler.java:29)
                at com.lmax.disruptor.BatchEventProcessor.processEvents(BatchEventProcessor.java:168)
                at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:125)
                at java.base/java.lang.Thread.run(Thread.java:829)

Thanks
Ranga

RE: Exception during accumulo init

Posted by dev1 <de...@etcoleman.com>.
Why do you keep using "-upload-accumulo-props~?  During initialization Accumulo will automatically read your site config file and then set properties in ZooKeeper accordingly.

Ed Coleman

From: Samudrala, Ranganath [USA] via user <us...@accumulo.apache.org>
Sent: Friday, January 20, 2023 10:48 AM
To: user@accumulo.apache.org
Subject: Re: Exception during accumulo init

I think this problem is resolved. Lower down in the log, after  I enter the credentials, I can see logs related to accumul/<instance_id>.

From: Samudrala, Ranganath [USA] via user <us...@accumulo.apache.org>>
Date: Friday, January 20, 2023 at 9:53 AM
To: Samudrala, Ranganath [USA] via user <us...@accumulo.apache.org>>
Subject: [External] Exception during accumulo init
Hello

The setup is in Kubernetes and Accumulo version is v2.10. None of the accumulo processes are running. Hadoop services are running is separate pods.  I open a shell in the Accumulo manager/master pod and invoked the command "accumulo init -upload-accumulo-props" .  I see an exception in the log and I am wondering if this is normal/acceptable or this problem should be resolved before attempting perform a start?

ERROR StatusLogger An exception occurred processing Appender MonitorLog
java.lang.RuntimeException: Accumulo not initialized, there is no instance id at hdfs://accumulo-hdfs-namenode-0.accumulo-hdfs-namenodes:8020/accumulo/instance_id
                at org.apache.accumulo.server.fs.VolumeManager.getInstanceIDFromHdfs(VolumeManager.java:218)
                at org.apache.accumulo.server.ServerInfo.<init>(ServerInfo.java:102)
                at org.apache.accumulo.server.ServerContext.<init>(ServerContext.java:106)
                at org.apache.accumulo.monitor.util.logging.AccumuloMonitorAppender.lambda$new$1(AccumuloMonitorAppender.java:93)
                at org.apache.accumulo.monitor.util.logging.AccumuloMonitorAppender.append(AccumuloMonitorAppender.java:111)
                at org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:161)
                at org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:134)
                at org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:125)
                at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:89)
                at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:683)
                at org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:641)
                at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:624)
                at org.apache.logging.log4j.core.config.LoggerConfig.logParent(LoggerConfig.java:674)
                at org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:643)
                at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:624)
                at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:612)
                at org.apache.logging.log4j.core.config.AwaitCompletionReliabilityStrategy.log(AwaitCompletionReliabilityStrategy.java:98)
                at org.apache.logging.log4j.core.async.AsyncLogger.actualAsyncLog(AsyncLogger.java:488)
                at org.apache.logging.log4j.core.async.RingBufferLogEvent.execute(RingBufferLogEvent.java:156)
                at org.apache.logging.log4j.core.async.RingBufferLogEventHandler.onEvent(RingBufferLogEventHandler.java:51)
                at org.apache.logging.log4j.core.async.RingBufferLogEventHandler.onEvent(RingBufferLogEventHandler.java:29)
                at com.lmax.disruptor.BatchEventProcessor.processEvents(BatchEventProcessor.java:168)
                at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:125)
                at java.base/java.lang.Thread.run(Thread.java:829)

Thanks
Ranga

Re: Exception during accumulo init

Posted by "Samudrala, Ranganath [USA] via user" <us...@accumulo.apache.org>.
I think this problem is resolved. Lower down in the log, after  I enter the credentials, I can see logs related to accumul/<instance_id>.

From: Samudrala, Ranganath [USA] via user <us...@accumulo.apache.org>
Date: Friday, January 20, 2023 at 9:53 AM
To: Samudrala, Ranganath [USA] via user <us...@accumulo.apache.org>
Subject: [External] Exception during accumulo init
Hello

The setup is in Kubernetes and Accumulo version is v2.10. None of the accumulo processes are running. Hadoop services are running is separate pods.  I open a shell in the Accumulo manager/master pod and invoked the command “accumulo init –upload-accumulo-props” .  I see an exception in the log and I am wondering if this is normal/acceptable or this problem should be resolved before attempting perform a start?

ERROR StatusLogger An exception occurred processing Appender MonitorLog
java.lang.RuntimeException: Accumulo not initialized, there is no instance id at hdfs://accumulo-hdfs-namenode-0.accumulo-hdfs-namenodes:8020/accumulo/instance_id
                at org.apache.accumulo.server.fs.VolumeManager.getInstanceIDFromHdfs(VolumeManager.java:218)
                at org.apache.accumulo.server.ServerInfo.<init>(ServerInfo.java:102)
                at org.apache.accumulo.server.ServerContext.<init>(ServerContext.java:106)
                at org.apache.accumulo.monitor.util.logging.AccumuloMonitorAppender.lambda$new$1(AccumuloMonitorAppender.java:93)
                at org.apache.accumulo.monitor.util.logging.AccumuloMonitorAppender.append(AccumuloMonitorAppender.java:111)
                at org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:161)
                at org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:134)
                at org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:125)
                at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:89)
                at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:683)
                at org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:641)
                at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:624)
                at org.apache.logging.log4j.core.config.LoggerConfig.logParent(LoggerConfig.java:674)
                at org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:643)
                at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:624)
                at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:612)
                at org.apache.logging.log4j.core.config.AwaitCompletionReliabilityStrategy.log(AwaitCompletionReliabilityStrategy.java:98)
                at org.apache.logging.log4j.core.async.AsyncLogger.actualAsyncLog(AsyncLogger.java:488)
                at org.apache.logging.log4j.core.async.RingBufferLogEvent.execute(RingBufferLogEvent.java:156)
                at org.apache.logging.log4j.core.async.RingBufferLogEventHandler.onEvent(RingBufferLogEventHandler.java:51)
                at org.apache.logging.log4j.core.async.RingBufferLogEventHandler.onEvent(RingBufferLogEventHandler.java:29)
                at com.lmax.disruptor.BatchEventProcessor.processEvents(BatchEventProcessor.java:168)
                at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:125)
                at java.base/java.lang.Thread.run(Thread.java:829)

Thanks
Ranga