Dang. Didn't save the log. Pardon me.
I pasted exceptions only and thought it all about 0x26ed968d880001
session but now I see that what I posted above has TIMED_OUT on
another session altogether. Above I skipped pasting exceptions
thinking them on the same session but now it seems they probabl
HI stack,
the other interesting part is with the session:
0x26ed968d880001
Looks like it gets disconnected from one of the servers (TIMEOUT). DO you
see any of these messages: "Attempting connection to server" in the logs
before you see all the consecutive
org.apache.zookeeper.ClientCnxn: Except
The thing that seems odd to me is that the connectivity complaints are
out of the zk client, right?, why is it failing getting to member 14
and why not move to another ensemble member if issue w/ 14?, and if
there were a general connectivity issue, I'd think that the running
hbase cluster would be
I also looked at the logs. Ted might have a point. It does look like that
zookeeper server's are doing fine (though as ted mentions the skew is a
little concerning, though that might be due to very few packets served by
the first server). Other than that the latencies of 300 ms at max should not
ca
Not sure this helps at all, but these times are remarkably asymmetrical. I
would expect members of a ZK cluster to have very comparable times.
Additionally, 345 ms is nowhere near large enough to cause a session to
expire. My take is that ZK doesn't think it caused the timeout.
On Mon, Feb 22,
Hey Lads:
Any chance of some pointers debugging a session TIMED OUT?
Client is hosted inside an hbase regionserver. Usually session
timeout is because of some fat GC pause that is longer than session
timeout but thats not the case here. It seems to be a connectivity
problem. Let me post a few
Wow, this is impressive. I haven't gotten a chance to try it yet but it
looks great. Thanks Mark!
If you are interested to have it included in the official ZooKeeper
release please submit a patch for contrib. It would be great to get this
included and pushed out to users as part of a release.
Thanks guys.
I don't have a strong use case but it did seem something of an
oddity/incompleteness when I was implementing the eclipse plug-in to
dynamically respond to znode changes. Without a Watcher available, it means
that ACL changes are the one instance where a user has to manually click
"Re
Feel free to enter JIRA(s) if you feel strongly. I agree with Ben in the
sense that I haven't heard of any use cases that require this, but a
JIRA with examples might strengthen the case.
Patrick
Benjamin Reed wrote:
no, you cannot watch for ACL changes. it is one of the
API/implementation si
no, you cannot watch for ACL changes. it is one of the
API/implementation simplifications we did since we didn't have a good
use case for it.
it does seem a little bit weird. we are following file system semantics
here. i guess for ultimate security only clients with admin permission
would be
Hi,
Does anyone know if there's a way to get a Watcher notification when a
znode's ACL changes?
I also wanted to ask if it seems weird that you can "read" a znode's ACL
even if you don't have permissions to read the data.
Thanks,
--
Mark Masse
http://www.massedynamic.org
Hi,
I have developed an Eclipse plug-in for Zookeeper. You can find out all
about it and download it from my website here:
http://www.massedynamic.org/eclipse/zookeeper/
I hope that you will find it useful.
--
Mark Masse
http://www.massedynamic.org
12 matches
Mail list logo