How is it possible to keep moving from CONNECTION_SUSPENDED to CONNECTION_LOST states and vice versa?
up vote
0
down vote
favorite
Our curator client kept moving from CONNECTION_SUSPENDED to CONNECTION_LOST multiple times without a single CONNECTION_RECONNECTED event.
I understand that a connection is susupended, when the curator is disconnected from Zookeeper on the network level. And the connection is lost, when curator beleives the session has expired.
But how is it possible that curator believes that the connection was suspended (lost, on the network level) even if we weren't connected once ?
We restarted Zookeeper, but it didn't fix anything and we had to restart the whole application to get connected again. Is this possible a problem with the Curator framework ? Because obviously it could've connected to Zookeeper, as it did after the restart.
apache-zookeeper apache-curator
add a comment |
up vote
0
down vote
favorite
Our curator client kept moving from CONNECTION_SUSPENDED to CONNECTION_LOST multiple times without a single CONNECTION_RECONNECTED event.
I understand that a connection is susupended, when the curator is disconnected from Zookeeper on the network level. And the connection is lost, when curator beleives the session has expired.
But how is it possible that curator believes that the connection was suspended (lost, on the network level) even if we weren't connected once ?
We restarted Zookeeper, but it didn't fix anything and we had to restart the whole application to get connected again. Is this possible a problem with the Curator framework ? Because obviously it could've connected to Zookeeper, as it did after the restart.
apache-zookeeper apache-curator
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Our curator client kept moving from CONNECTION_SUSPENDED to CONNECTION_LOST multiple times without a single CONNECTION_RECONNECTED event.
I understand that a connection is susupended, when the curator is disconnected from Zookeeper on the network level. And the connection is lost, when curator beleives the session has expired.
But how is it possible that curator believes that the connection was suspended (lost, on the network level) even if we weren't connected once ?
We restarted Zookeeper, but it didn't fix anything and we had to restart the whole application to get connected again. Is this possible a problem with the Curator framework ? Because obviously it could've connected to Zookeeper, as it did after the restart.
apache-zookeeper apache-curator
Our curator client kept moving from CONNECTION_SUSPENDED to CONNECTION_LOST multiple times without a single CONNECTION_RECONNECTED event.
I understand that a connection is susupended, when the curator is disconnected from Zookeeper on the network level. And the connection is lost, when curator beleives the session has expired.
But how is it possible that curator believes that the connection was suspended (lost, on the network level) even if we weren't connected once ?
We restarted Zookeeper, but it didn't fix anything and we had to restart the whole application to get connected again. Is this possible a problem with the Curator framework ? Because obviously it could've connected to Zookeeper, as it did after the restart.
apache-zookeeper apache-curator
apache-zookeeper apache-curator
asked Nov 9 at 20:51
Muhammad Gelbana
2,39022862
2,39022862
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53233110%2fhow-is-it-possible-to-keep-moving-from-connection-suspended-to-connection-lost-s%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown