accumulo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wyatt Frelot <>
Subject Re: Failed to connect to zookeeper within 2x ZK timeout period 30000
Date Mon, 02 Feb 2015 22:26:34 GMT
I have been looking in the logs and I found something…just not sure about it’s impact:
2015-02-02 22:21:04,390 [server.Accumulo] WARN : System swappiness setting is greater than
ten (60) which can cause time-sensitive operations to be delayed.  Accumulo is time sensitive
because it needs to maintain distributed lock agreement.

Would this cause it?

On Feb 2, 2015, at 17:03, John Vines <<>>

I'm sorry, I meant nmode:2181 in your actual code.

On Mon, Feb 2, 2015 at 4:53 PM, Wyatt Frelot <<>>

I think I did it right. Here is what I get when I  run it the way that you suggested.

vagrant@mnode:/cloud/accumulo/lib$ nc mnode:2181
This is nc from the netcat-openbsd package. An alternative nc is available
in the netcat-traditional package.
usage: nc [-46bCDdhjklnrStUuvZz] [-I length] [-i interval] [-O length]
  [-P proxy_username] [-p source_port] [-q seconds] [-s source]
  [-T toskeyword] [-V rtable] [-w timeout] [-X proxy_protocol]
  [-x proxy_address[:port]] [destination] [port]

On Feb 2, 2015, at 16:38, John Vines <<>>

It looks like you're declaring your ZK connect string as "mnode". What happens if you do "mnode:2181"?

On Mon, Feb 2, 2015 at 4:17 PM, Wyatt Frelot <<>>

If I am reading this correctly, it appears as if everything is in order:

vagrant@mnode:/vagrant$ nc mnode 2181
Zookeeper version: 3.4.6-1569965, built on 02/20/2014 09:09 GMT

Latency min/avg/max: 0/0/62
Received: 3114
Sent: 3162
Connections: 8
Outstanding: 0
Zxid: 0x71a
Mode: standalone
Node count: 270

On Feb 2, 2015, at 16:06, Mike Drob <<>>

nc [zk-host] [zk-port]


View raw message