Ranga, Your current error message seems to point to your root tablet not being able to be created (or assigned). I would start by trying to verify that HDFS is functional and that your `instance.volumes` entries include a valid HDFS volume entry.
Does your monitor page report additional errors? - Daniel On Tue, Feb 21, 2023 at 1:43 PM Samudrala, Ranganath [USA] via user < user@accumulo.apache.org> wrote: > Hello, > > Accumulo is running in Kubernetes cluster. Metdata data is stored in HDFS > and table data is stored in Amazon S3. No attempt has been made yet to > store/insert table data. But, when I attempt to create a table in > Accumulo via Java API, I see the following error. > > > WARN : org.apache.accumulo.core.clientImpl.ThriftTransportPool - Thread > "main" stuck on IO to accumulo-masters-0.accumulo-masters.acc > umulo-k8s.svc.cluster.local:9999 (0) for at least 120033 ms > > > > I see the below error in T-SERVER logs: > > 2023-02-21 18:04:09,373 WARN [Root tablet assignment retry] > [org.apache.accumulo.tserver.TabletServer]: exception trying to assign tablet > +r<< > hdfs://accumulo-hdfs-namenode-0.accumulo-hdfs-namenodes:8020/accumulo/tables/+r/root_tablet > java.lang.NullPointerException > at > org.apache.accumulo.server.tablets.TabletTime.getInstance(TabletTime.java:60) > at org.apache.accumulo.tserver.tablet.Tablet.<init>(Tablet.java:341) > at > org.apache.accumulo.tserver.TabletServer$AssignmentHandler.run(TabletServer.java:2504) > at > org.apache.accumulo.fate.util.LoggingRunnable.run(LoggingRunnable.java:35) > at java.lang.Thread.run(Thread.java:750) > 2023-02-21 18:04:09,374 WARN [Root tablet assignment retry] > [org.apache.accumulo.tserver.TabletServer]: failed to open tablet +r<< > reporting failure to master > 2023-02-21 18:04:09,374 WARN [Root tablet assignment retry] > [org.apache.accumulo.tserver.TabletServer]: rescheduling tablet load in > 600.00 seconds > 2023-02-21 18:07:03,210 WARN [SimpleTimer-0] > [org.apache.accumulo.server.ServerUtil]: System swappiness setting is greater > than ten (30) which can cause time-sensitive operations to be delayed. > Accumulo is time sensitive because it needs to maintain distributed lock > agreement. > > > > The installed configuration is made up of 2 instances of HDFS data nodes, > 2 instances of T-SERVERs, 1 instance each of HDFS name node and Accumulo > master. > > > config -t accumulo.root > . > default | table.file.replication ........................ | 0 > site | @override .................................. | 2 > table | @override .................................. | 5 > . > . > > config -t accumulo.metadata > . > default | table.file.replication ........................ | 0 > site | @override .................................. | 2 > table | @override .................................. | 5 > . > > How do I fix this problem? > > Thanks in advance. > Ranga > >
