[jira] [Updated] (BOOKKEEPER-594) AutoRecovery shutting down on SyncDisconnected
[ https://issues.apache.org/jira/browse/BOOKKEEPER-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-594: -- Fix Version/s: (was: 4.3.0) 4.4.0 > AutoRecovery shutting down on SyncDisconnected > -- > > Key: BOOKKEEPER-594 > URL: https://issues.apache.org/jira/browse/BOOKKEEPER-594 > Project: Bookkeeper > Issue Type: Bug > Components: bookkeeper-auto-recovery >Reporter: Ivan Kelly >Assignee: Ivan Kelly >Priority: Critical > Fix For: 4.4.0 > > Attachments: BOOKKEEPER-594.diff > > > Currently the AutoRecovery daemon will shut down on SyncDisconnected. This is > the wrong behaviour. It should wait until it gets a expired signal before > shutting down. If autoRecoveryDaemonEnabled=true, then the autorecovery > deamon is running in the same process as the bookie, the bookie death watcher > will take down the bookie at this point also, but as the bookie hasn't > shutdown, exit code will be 0, which is confusing to any monitoring app. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (BOOKKEEPER-594) AutoRecovery shutting down on SyncDisconnected
[ https://issues.apache.org/jira/browse/BOOKKEEPER-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R updated BOOKKEEPER-594: Component/s: bookkeeper-auto-recovery > AutoRecovery shutting down on SyncDisconnected > -- > > Key: BOOKKEEPER-594 > URL: https://issues.apache.org/jira/browse/BOOKKEEPER-594 > Project: Bookkeeper > Issue Type: Bug > Components: bookkeeper-auto-recovery >Reporter: Ivan Kelly >Assignee: Ivan Kelly >Priority: Critical > Fix For: 4.3.0 > > Attachments: BOOKKEEPER-594.diff > > > Currently the AutoRecovery daemon will shut down on SyncDisconnected. This is > the wrong behaviour. It should wait until it gets a expired signal before > shutting down. If autoRecoveryDaemonEnabled=true, then the autorecovery > deamon is running in the same process as the bookie, the bookie death watcher > will take down the bookie at this point also, but as the bookie hasn't > shutdown, exit code will be 0, which is confusing to any monitoring app. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (BOOKKEEPER-594) AutoRecovery shutting down on SyncDisconnected
[ https://issues.apache.org/jira/browse/BOOKKEEPER-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Merli updated BOOKKEEPER-594: Attachment: BOOKKEEPER-594.diff Proposed patch to make the ReplicationWorker more resilient to exceptions > AutoRecovery shutting down on SyncDisconnected > -- > > Key: BOOKKEEPER-594 > URL: https://issues.apache.org/jira/browse/BOOKKEEPER-594 > Project: Bookkeeper > Issue Type: Bug >Reporter: Ivan Kelly >Assignee: Ivan Kelly >Priority: Critical > Fix For: 4.3.0 > > Attachments: BOOKKEEPER-594.diff > > > Currently the AutoRecovery daemon will shut down on SyncDisconnected. This is > the wrong behaviour. It should wait until it gets a expired signal before > shutting down. If autoRecoveryDaemonEnabled=true, then the autorecovery > deamon is running in the same process as the bookie, the bookie death watcher > will take down the bookie at this point also, but as the bookie hasn't > shutdown, exit code will be 0, which is confusing to any monitoring app. -- This message was sent by Atlassian JIRA (v6.1#6144)
