[
https://issues.apache.org/jira/browse/ZOOKEEPER-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374026#comment-15374026
]
Michael Han commented on ZOOKEEPER-2152:
----------------------------------------
I think what you pointed out on "it is utilized only after a successful
connection attempt" is about correct - we did hit that bug because we always
ends up here in zookeeper_interest, for this reconfig test due to the fake
servers:
{code}
// No need to delay -- grab the next server and attempt connection
zoo_cycle_next_server(zh);
zh->fd = socket(zh->addr_cur.ss_family, SOCK_STREAM, 0);
if (zh->fd < 0) {
rc = handle_socket_error_msg(zh,
__LINE__,
ZSYSTEMERROR,
"socket() call failed");
return api_epilog(zh, rc);
}
{code}
So the handle_error has no chance to get invoked.
> Intermittent failure in TestReconfig.cc
> ---------------------------------------
>
> Key: ZOOKEEPER-2152
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2152
> Project: ZooKeeper
> Issue Type: Sub-task
> Components: c client
> Reporter: Michi Mutsuzaki
> Assignee: Michael Han
> Labels: reconfiguration
> Fix For: 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2152.patch
>
>
> I'm seeing this failure in the c client test once in a while:
> {noformat}
> [exec]
> /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/src/c/tests/TestReconfig.cc:474:
> Assertion: assertion failed [Expression: found != string::npos,
> 10.10.10.4:2004 not in newComing list]
> {noformat}
> https://builds.apache.org/job/ZooKeeper-trunk/2640/console
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
