zookeeper: WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /127.0.0.1 - max is 10
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OEM Priority Project |
Fix Released
|
High
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned | ||
Raring |
Fix Released
|
High
|
Unassigned | ||
Saucy |
Fix Released
|
Undecided
|
Unassigned | ||
juju (Ubuntu) |
Fix Committed
|
High
|
Kapil Thangavelu |
Bug Description
I'm running juju 0.6-1ubuntu1 on a quantal/maas cloud of highbank/maas nodes. I have a demo loop that I run to deploy hadoop, wait, add a few nodes, wait add a few more nodes, then tear things down to just the bootstrap node & restart. I'm finding that this will very quickly cause a hang where any juju command fails to make progress.
ubuntu@laptop:~$ juju status
2012-10-23 13:34:17,456 INFO Connecting to environment...
<hang>
Manually inspecting the bootstrap node shows that the ssh connection does occur - and until I ^c the juju command, /var/log/
2012-10-23 15:43:16,754 - WARN [NIOServerCxn.
netstat output doesn't suggest a ton of active connections - I'll attach a copy of this output in case it helps.
I've also found that running "sudo restart zookeeper" on the node frees it up, and I can again run juju commands.
See demo.sh in lp:~dannf/+junk/arm-maas-demo to see what this sample code looks like. Dropping the "sleep" timeouts to a low value - e.g. 10s - seems to make the hang occur faster.
Changed in oem-priority: | |
importance: | Undecided → High |
Changed in juju (Ubuntu): | |
assignee: | nobody → Kapil Thangavelu (hazmat) |
status: | Confirmed → In Progress |
Note that the zookeeper process appears to be spinning, not just hung.