You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@accumulo.apache.org by Jayesh Patel <jp...@keywcorp.com> on 2016/12/01 22:24:27 UTC
openjdk, Accumulo master state doesn't change from HAVE_LOCK to
NORMAL
Accumulo 1.7.0 with HDFS 2.7.1
I was experimenting with openjdk instead of Oracle JRE for Accumulo and ran
into this issue. It seems like because it never transitions from HAVE_LOCK
to NORMAL, it never gets around to start the thrift server. Changing back
to Oracle JRE didn't make a difference.
Here's what I get in the logs for the master:
2016-12-01 17:01:07,970 [trace.DistributedTrace] INFO : SpanReceiver
org.apache.accumulo.tracer.ZooTraceCli
ent was loaded successfully.
2016-12-01 17:01:07,971 [master.Master] INFO : trying to get master lock
2016-12-01 17:01:07,987 [master.EventCoordinator] INFO : State changed from
INITIAL to HAVE_LOCK
2016-12-01 17:01:08,038 [master.Master] INFO : New servers:
[instance-accumulo:9997[258ac79197e000d]]
On the successful install it transitions right away to NORMAL and goes on
the listen on port 9999:
2015-06-07 17:50:35,393 [master.Master] INFO : trying to get master lock
2015-06-07 17:50:35,408 [master.EventCoordinator] INFO : State changed from
INITIAL to HAVE_LOCK
2015-06-07 17:50:35,432 [master.EventCoordinator] INFO : State changed from
HAVE_LOCK to NORMAL
2015-06-07 17:50:35,524 [balancer.TableLoadBalancer] INFO : Loaded class
org.apache.accumulo.server.master.balancer.DefaultLoadBalancer for table !0
2015-06-07 17:50:35,631 [master.Master] INFO : Setting master lock data to
127.0.0.1:9999
I found ACCUMULO-4513 <https://issues.apache.org/jira/browse/ACCUMULO-4513>
, but it doesn't seem relevant as I didn't try to stop.
Any ideas as to what is going on?
HDFS seems fine based on my limited tests with openjdk 1.8. I did find some
old posts about Accumulo issues with IBM JDK. Should I expect Accumulo to
work with openjdk?
Thank you,
Jayesh
Re: openjdk, Accumulo master state doesn't change from HAVE_LOCK to NORMAL
Posted by Christopher <ct...@apache.org>.
I can't be sure why the master is stuck in that state. It could be a bug in
1.7.0. Can you reproduce in 1.7.2?
On Thu, Dec 1, 2016 at 5:56 PM Jayesh Patel <jp...@keywcorp.com> wrote:
> Thank you!
>
>
>
> What might be going on with the state transition of the master? Looks
> like the tservers can’t talk to the master without the thrift interface.
> Is there another interface I can enable on the master?
>
>
>
>
>
> *From:* Christopher [mailto:ctubbsii@apache.org]
> *Sent:* Thursday, December 01, 2016 5:34 PM
> *To:* user@accumulo.apache.org
> *Subject:* Re: openjdk, Accumulo master state doesn't change from
> HAVE_LOCK to NORMAL
>
>
>
> This issue described doesn't seem related to the JDK. Yes, you should
> expect Accumulo to work with OpenJDK. While we don't prescribe a JDK for
> users, most of the developers have an interest in ensuring at least OpenJDK
> and Oracle JDK work well. A few people care about IBM JDK also, and we
> accept contributions to fix issues relevant to IBM JDK.
>
> Personally, I use OpenJDK 8 exclusively, and haven't seen this issue.
>
>
>
> On Thu, Dec 1, 2016 at 5:24 PM Jayesh Patel <jp...@keywcorp.com> wrote:
>
> Accumulo 1.7.0 with HDFS 2.7.1
>
>
>
> I was experimenting with openjdk instead of Oracle JRE for Accumulo and
> ran into this issue. It seems like because it never transitions from
> HAVE_LOCK to NORMAL, it never gets around to start the thrift server.
> Changing back to Oracle JRE didn’t make a difference.
>
>
>
> Here’s what I get in the logs for the master:
>
> 2016-12-01 17:01:07,970 [trace.DistributedTrace] INFO : SpanReceiver
> org.apache.accumulo.tracer.ZooTraceCli
>
> ent was loaded successfully.
>
> 2016-12-01 17:01:07,971 [master.Master] INFO : trying to get master lock
>
> 2016-12-01 17:01:07,987 [master.EventCoordinator] INFO : State changed
> from INITIAL to HAVE_LOCK
>
> 2016-12-01 17:01:08,038 [master.Master] INFO : New servers:
> [instance-accumulo:9997[258ac79197e000d]]
>
>
>
> On the successful install it transitions right away to NORMAL and goes on
> the listen on port 9999:
>
> 2015-06-07 17:50:35,393 [master.Master] INFO : trying to get master lock
>
> 2015-06-07 17:50:35,408 [master.EventCoordinator] INFO : State changed
> from INITIAL to HAVE_LOCK
>
> 2015-06-07 17:50:35,432 [master.EventCoordinator] INFO : State changed
> from HAVE_LOCK to NORMAL
>
> 2015-06-07 17:50:35,524 [balancer.TableLoadBalancer] INFO : Loaded class
> org.apache.accumulo.server.master.balancer.DefaultLoadBalancer for table !0
>
> 2015-06-07 17:50:35,631 [master.Master] INFO : Setting master lock data to
> 127.0.0.1:9999
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__127.0.0.1-3A9999&d=DQMFaQ&c=31nHN1tvZeuWBT6LwDN4Ngk1qezfsYHyolgGeY2ZhlU&r=yH4vdeYURv2hJ1Gmntk0uc08nV-pgsJRlR6tfCR4KBw&m=PGaErZqBG4ZLhvBF_e2erg7tdil5yjEujZQMiKmp5Uk&s=TagTSNKkbvhsYiu5geGRtorEBK2ghw6Y8KvzKV2OWdE&e=>
>
>
>
> I found ACCUMULO-4513
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_ACCUMULO-2D4513&d=DQMFaQ&c=31nHN1tvZeuWBT6LwDN4Ngk1qezfsYHyolgGeY2ZhlU&r=yH4vdeYURv2hJ1Gmntk0uc08nV-pgsJRlR6tfCR4KBw&m=PGaErZqBG4ZLhvBF_e2erg7tdil5yjEujZQMiKmp5Uk&s=SNeP9F29b0ONCVeuddUvGx0xdd8Z3TLD-OxqjZsHa_s&e=>,
> but it doesn’t seem relevant as I didn’t try to stop.
>
>
>
> Any ideas as to what is going on?
>
>
>
> HDFS seems fine based on my limited tests with openjdk 1.8. I did find
> some old posts about Accumulo issues with IBM JDK. Should I expect
> Accumulo to work with openjdk?
>
>
>
> Thank you,
> Jayesh
>
>
>
>
RE: openjdk, Accumulo master state doesn't change from HAVE_LOCK to
NORMAL
Posted by Jayesh Patel <jp...@keywcorp.com>.
Thank you!
What might be going on with the state transition of the master? Looks like the tservers can’t talk to the master without the thrift interface. Is there another interface I can enable on the master?
From: Christopher [mailto:ctubbsii@apache.org]
Sent: Thursday, December 01, 2016 5:34 PM
To: user@accumulo.apache.org
Subject: Re: openjdk, Accumulo master state doesn't change from HAVE_LOCK to NORMAL
This issue described doesn't seem related to the JDK. Yes, you should expect Accumulo to work with OpenJDK. While we don't prescribe a JDK for users, most of the developers have an interest in ensuring at least OpenJDK and Oracle JDK work well. A few people care about IBM JDK also, and we accept contributions to fix issues relevant to IBM JDK.
Personally, I use OpenJDK 8 exclusively, and haven't seen this issue.
On Thu, Dec 1, 2016 at 5:24 PM Jayesh Patel <jpatel@keywcorp.com <ma...@keywcorp.com> > wrote:
Accumulo 1.7.0 with HDFS 2.7.1
I was experimenting with openjdk instead of Oracle JRE for Accumulo and ran into this issue. It seems like because it never transitions from HAVE_LOCK to NORMAL, it never gets around to start the thrift server. Changing back to Oracle JRE didn’t make a difference.
Here’s what I get in the logs for the master:
2016-12-01 17:01:07,970 [trace.DistributedTrace] INFO : SpanReceiver org.apache.accumulo.tracer.ZooTraceCli
ent was loaded successfully.
2016-12-01 17:01:07,971 [master.Master] INFO : trying to get master lock
2016-12-01 17:01:07,987 [master.EventCoordinator] INFO : State changed from INITIAL to HAVE_LOCK
2016-12-01 17:01:08,038 [master.Master] INFO : New servers: [instance-accumulo:9997[258ac79197e000d]]
On the successful install it transitions right away to NORMAL and goes on the listen on port 9999:
2015-06-07 17:50:35,393 [master.Master] INFO : trying to get master lock
2015-06-07 17:50:35,408 [master.EventCoordinator] INFO : State changed from INITIAL to HAVE_LOCK
2015-06-07 17:50:35,432 [master.EventCoordinator] INFO : State changed from HAVE_LOCK to NORMAL
2015-06-07 17:50:35,524 [balancer.TableLoadBalancer] INFO : Loaded class org.apache.accumulo.server.master.balancer.DefaultLoadBalancer for table !0
2015-06-07 17:50:35,631 [master.Master] INFO : Setting master lock data to 127.0.0.1:9999 <https://urldefense.proofpoint.com/v2/url?u=http-3A__127.0.0.1-3A9999&d=DQMFaQ&c=31nHN1tvZeuWBT6LwDN4Ngk1qezfsYHyolgGeY2ZhlU&r=yH4vdeYURv2hJ1Gmntk0uc08nV-pgsJRlR6tfCR4KBw&m=PGaErZqBG4ZLhvBF_e2erg7tdil5yjEujZQMiKmp5Uk&s=TagTSNKkbvhsYiu5geGRtorEBK2ghw6Y8KvzKV2OWdE&e=>
I found ACCUMULO-4513 <https://urldefense.proofpoint.com/v2/url?u=https-3A__issues.apache.org_jira_browse_ACCUMULO-2D4513&d=DQMFaQ&c=31nHN1tvZeuWBT6LwDN4Ngk1qezfsYHyolgGeY2ZhlU&r=yH4vdeYURv2hJ1Gmntk0uc08nV-pgsJRlR6tfCR4KBw&m=PGaErZqBG4ZLhvBF_e2erg7tdil5yjEujZQMiKmp5Uk&s=SNeP9F29b0ONCVeuddUvGx0xdd8Z3TLD-OxqjZsHa_s&e=> , but it doesn’t seem relevant as I didn’t try to stop.
Any ideas as to what is going on?
HDFS seems fine based on my limited tests with openjdk 1.8. I did find some old posts about Accumulo issues with IBM JDK. Should I expect Accumulo to work with openjdk?
Thank you,
Jayesh
Re: openjdk, Accumulo master state doesn't change from HAVE_LOCK to NORMAL
Posted by Christopher <ct...@apache.org>.
This issue described doesn't seem related to the JDK. Yes, you should
expect Accumulo to work with OpenJDK. While we don't prescribe a JDK for
users, most of the developers have an interest in ensuring at least OpenJDK
and Oracle JDK work well. A few people care about IBM JDK also, and we
accept contributions to fix issues relevant to IBM JDK.
Personally, I use OpenJDK 8 exclusively, and haven't seen this issue.
On Thu, Dec 1, 2016 at 5:24 PM Jayesh Patel <jp...@keywcorp.com> wrote:
> Accumulo 1.7.0 with HDFS 2.7.1
>
>
>
> I was experimenting with openjdk instead of Oracle JRE for Accumulo and
> ran into this issue. It seems like because it never transitions from
> HAVE_LOCK to NORMAL, it never gets around to start the thrift server.
> Changing back to Oracle JRE didn’t make a difference.
>
>
>
> Here’s what I get in the logs for the master:
>
> 2016-12-01 17:01:07,970 [trace.DistributedTrace] INFO : SpanReceiver
> org.apache.accumulo.tracer.ZooTraceCli
>
> ent was loaded successfully.
>
> 2016-12-01 17:01:07,971 [master.Master] INFO : trying to get master lock
>
> 2016-12-01 17:01:07,987 [master.EventCoordinator] INFO : State changed
> from INITIAL to HAVE_LOCK
>
> 2016-12-01 17:01:08,038 [master.Master] INFO : New servers:
> [instance-accumulo:9997[258ac79197e000d]]
>
>
>
> On the successful install it transitions right away to NORMAL and goes on
> the listen on port 9999:
>
> 2015-06-07 17:50:35,393 [master.Master] INFO : trying to get master lock
>
> 2015-06-07 17:50:35,408 [master.EventCoordinator] INFO : State changed
> from INITIAL to HAVE_LOCK
>
> 2015-06-07 17:50:35,432 [master.EventCoordinator] INFO : State changed
> from HAVE_LOCK to NORMAL
>
> 2015-06-07 17:50:35,524 [balancer.TableLoadBalancer] INFO : Loaded class
> org.apache.accumulo.server.master.balancer.DefaultLoadBalancer for table !0
>
> 2015-06-07 17:50:35,631 [master.Master] INFO : Setting master lock data to
> 127.0.0.1:9999
>
>
>
> I found ACCUMULO-4513
> <https://issues.apache.org/jira/browse/ACCUMULO-4513>, but it doesn’t
> seem relevant as I didn’t try to stop.
>
>
>
> Any ideas as to what is going on?
>
>
>
> HDFS seems fine based on my limited tests with openjdk 1.8. I did find
> some old posts about Accumulo issues with IBM JDK. Should I expect
> Accumulo to work with openjdk?
>
>
>
> Thank you,
> Jayesh
>
>
>
Re: openjdk, Accumulo master state doesn't change from HAVE_LOCK to NORMAL
Posted by Keith Turner <ke...@deenlo.com>.
I use openjdk8 from Ubuntu 16.04 and Centos 7 packages to run Accumulo
all the time without issue.
On Thu, Dec 1, 2016 at 5:24 PM, Jayesh Patel <jp...@keywcorp.com> wrote:
> Accumulo 1.7.0 with HDFS 2.7.1
>
>
>
> I was experimenting with openjdk instead of Oracle JRE for Accumulo and ran
> into this issue. It seems like because it never transitions from HAVE_LOCK
> to NORMAL, it never gets around to start the thrift server. Changing back
> to Oracle JRE didn’t make a difference.
>
>
>
> Here’s what I get in the logs for the master:
>
> 2016-12-01 17:01:07,970 [trace.DistributedTrace] INFO : SpanReceiver
> org.apache.accumulo.tracer.ZooTraceCli
>
> ent was loaded successfully.
>
> 2016-12-01 17:01:07,971 [master.Master] INFO : trying to get master lock
>
> 2016-12-01 17:01:07,987 [master.EventCoordinator] INFO : State changed from
> INITIAL to HAVE_LOCK
>
> 2016-12-01 17:01:08,038 [master.Master] INFO : New servers:
> [instance-accumulo:9997[258ac79197e000d]]
>
>
>
> On the successful install it transitions right away to NORMAL and goes on
> the listen on port 9999:
>
> 2015-06-07 17:50:35,393 [master.Master] INFO : trying to get master lock
>
> 2015-06-07 17:50:35,408 [master.EventCoordinator] INFO : State changed from
> INITIAL to HAVE_LOCK
>
> 2015-06-07 17:50:35,432 [master.EventCoordinator] INFO : State changed from
> HAVE_LOCK to NORMAL
>
> 2015-06-07 17:50:35,524 [balancer.TableLoadBalancer] INFO : Loaded class
> org.apache.accumulo.server.master.balancer.DefaultLoadBalancer for table !0
>
> 2015-06-07 17:50:35,631 [master.Master] INFO : Setting master lock data to
> 127.0.0.1:9999
>
>
>
> I found ACCUMULO-4513, but it doesn’t seem relevant as I didn’t try to stop.
>
>
>
> Any ideas as to what is going on?
>
>
>
> HDFS seems fine based on my limited tests with openjdk 1.8. I did find some
> old posts about Accumulo issues with IBM JDK. Should I expect Accumulo to
> work with openjdk?
>
>
>
> Thank you,
> Jayesh
>
>
Re: openjdk, Accumulo master state doesn't change from HAVE_LOCK to NORMAL
Posted by Keith Turner <ke...@deenlo.com>.
If you run netstat -nape, do you see the master process listening on
anything? Maybe its listening on another interface or IP6?
On Thu, Dec 1, 2016 at 5:24 PM, Jayesh Patel <jp...@keywcorp.com> wrote:
> Accumulo 1.7.0 with HDFS 2.7.1
>
>
>
> I was experimenting with openjdk instead of Oracle JRE for Accumulo and ran
> into this issue. It seems like because it never transitions from HAVE_LOCK
> to NORMAL, it never gets around to start the thrift server. Changing back
> to Oracle JRE didn’t make a difference.
>
>
>
> Here’s what I get in the logs for the master:
>
> 2016-12-01 17:01:07,970 [trace.DistributedTrace] INFO : SpanReceiver
> org.apache.accumulo.tracer.ZooTraceCli
>
> ent was loaded successfully.
>
> 2016-12-01 17:01:07,971 [master.Master] INFO : trying to get master lock
>
> 2016-12-01 17:01:07,987 [master.EventCoordinator] INFO : State changed from
> INITIAL to HAVE_LOCK
>
> 2016-12-01 17:01:08,038 [master.Master] INFO : New servers:
> [instance-accumulo:9997[258ac79197e000d]]
>
>
>
> On the successful install it transitions right away to NORMAL and goes on
> the listen on port 9999:
>
> 2015-06-07 17:50:35,393 [master.Master] INFO : trying to get master lock
>
> 2015-06-07 17:50:35,408 [master.EventCoordinator] INFO : State changed from
> INITIAL to HAVE_LOCK
>
> 2015-06-07 17:50:35,432 [master.EventCoordinator] INFO : State changed from
> HAVE_LOCK to NORMAL
>
> 2015-06-07 17:50:35,524 [balancer.TableLoadBalancer] INFO : Loaded class
> org.apache.accumulo.server.master.balancer.DefaultLoadBalancer for table !0
>
> 2015-06-07 17:50:35,631 [master.Master] INFO : Setting master lock data to
> 127.0.0.1:9999
>
>
>
> I found ACCUMULO-4513, but it doesn’t seem relevant as I didn’t try to stop.
>
>
>
> Any ideas as to what is going on?
>
>
>
> HDFS seems fine based on my limited tests with openjdk 1.8. I did find some
> old posts about Accumulo issues with IBM JDK. Should I expect Accumulo to
> work with openjdk?
>
>
>
> Thank you,
> Jayesh
>
>