[
https://issues.apache.org/jira/browse/ZOOKEEPER-907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925541#action_12925541
]
Vishal K commented on ZOOKEEPER-907:
------------------------------------
It did occur to me. I thought this was by design for sync? sync() is an async
call. So the caller never gets any exceptions unless a callback is specified.
I might be worng here though, I am still reading the code to understand how
sync works.
> Spurious "KeeperErrorCode = Session moved" messages
> ---------------------------------------------------
>
> Key: ZOOKEEPER-907
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-907
> Project: Zookeeper
> Issue Type: Bug
> Affects Versions: 3.3.1
> Reporter: Vishal K
> Assignee: Vishal K
> Priority: Blocker
> Fix For: 3.3.2, 3.4.0
>
> Attachments: ZOOKEEPER-907.patch, ZOOKEEPER-907.patch_v2
>
>
> The sync request does not set the session owner in Request.
> As a result, the leader keeps printing:
> 2010-07-01 10:55:36,733 - INFO [ProcessThread:-1:preprequestproces...@405] -
> Got user-level KeeperException when processing sessionid:0x298d3b1fa90000
> type:sync: cxid:0x6 zxid:0xfffffffffffffffe txntype:unknown reqpath:/ Error
> Path:null Error:KeeperErrorCode = Session moved
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
