Good afternoon all,
I just literally started having this problem on Friday. My code worked
previously (1mo ago) but I came back to it and I have not been able to resolve
this problem since I have started experiencing it. So, I am seeking guidance
and assistance.
I have a Vagrant cluster setup
I meant ZK 3.4.6.
Wyatt
On Feb 2, 2015, at 15:58, Wyatt Frelot
mailto:wyatt.fre...@altamiracorp.com>> wrote:
Good afternoon all,
I just literally started having this problem on Friday. My code worked
previously (1mo ago) but I came back to it and I have not been able to resolve
this problem s
Can you verify that zookeeper is running and accepting connections?
nc [zk-host] [zk-port]
> stat
And see that it does not result in error.
On Mon, Feb 2, 2015 at 2:58 PM, Wyatt Frelot
wrote:
> Good afternoon all,
>
> I just literally started having this problem on Friday. My code worked
> p
Mike
If I am reading this correctly, it appears as if everything is in order:
vagrant@mnode:/vagrant$ nc mnode 2181
stat
Zookeeper version: 3.4.6-1569965, built on 02/20/2014 09:09 GMT
Clients:
/192.168.15.4:44488[1](queued=0,recved=84,sent=85)
/192.168.15.2:48504[0](queued=0,recved=1,sent=0)
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
wrote:
> Mike
>
> If I am reading this correctly, it appears as if everything is in order:
>
> vagrant@mnode:/vagrant$ nc mnode 2181
> stat
> Zoo
John,
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'm sorry, I meant nmode:2181 in your actual code.
On Mon, Feb 2, 2015 at 4:53 PM, Wyatt Frelot
wrote:
> John,
>
> 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
John,
Yes, I tried that and the same thing happens.
Sent from OWA on Android
From: John Vines
Sent: Monday, February 2, 2015 5:03:04 PM
To: user@accumulo.apache.org
Subject: Re: Failed to connect to zookeeper within 2x ZK timeout period 3
I'm sorry, I meant
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 main
See swappiness: http://en.wikipedia.org/wiki/Swappiness
$ cat /proc/sys/vm/swappiness
# echo 20 > /proc/sys/vm/swappiness
tl;dr Having a "large" value for swappiness might cause the operating system to move your
process to "swap" instead of main memory which would likely cause it to lose its
Good evening all,
Thanks for the replies. I found the problem. Somehow my /etc/hosts file was
changed for the zookeeper node which was the issue.
Isolated the problem by swapping node name for IP address and started receiving
Unknown Host errors which led me to the client’s etc/hosts file.
Tha
11 matches
Mail list logo
