[jira] [Commented] (RATIS-622) createLog will block indefinitely if group creation fails

[ https://issues.apache.org/jira/browse/RATIS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885646#comment-16885646 ] Ankit Singhal commented on RATIS-622: - +1, looks good to me [~elserj]. Maybe once we

[jira] [Comment Edited] (RATIS-556) Detect node failures and add other workers to group serving the log and replicate the data of the log

[ https://issues.apache.org/jira/browse/RATIS-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885631#comment-16885631 ] Ankit Singhal edited comment on RATIS-556 at 7/15/19 9:24 PM: --

[jira] [Commented] (RATIS-556) Detect node failures and add other workers to group serving the log and replicate the data of the log

[ https://issues.apache.org/jira/browse/RATIS-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885631#comment-16885631 ] Ankit Singhal commented on RATIS-556: - {code} Failed to read from log org.apache.ratis

[jira] [Commented] (RATIS-611) Add a test for InstallSnapshotNotification with follower restart

[ https://issues.apache.org/jira/browse/RATIS-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885490#comment-16885490 ] Tsz Wo Nicholas Sze commented on RATIS-611: --- The test failures are not related.

[jira] [Commented] (RATIS-618) Ratis leader should notify stateMachine if the commit index gap between leader and follower is high

[ https://issues.apache.org/jira/browse/RATIS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885480#comment-16885480 ] Tsz Wo Nicholas Sze commented on RATIS-618: --- We may just pass the CommitInfo the

[jira] [Commented] (RATIS-307) Improve make_rc script with additional step of the release process.

[ https://issues.apache.org/jira/browse/RATIS-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885477#comment-16885477 ] Tsz Wo Nicholas Sze commented on RATIS-307: --- +1 PR looks good. One problem with

[jira] [Commented] (RATIS-609) Change RaftLog to use RaftGroupMemberId

[ https://issues.apache.org/jira/browse/RATIS-609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885463#comment-16885463 ] Tsz Wo Nicholas Sze commented on RATIS-609: --- The patch depends on RATIS-611. >

[jira] [Commented] (RATIS-606) GrpcService should use SO_REUSEADDR flag

[ https://issues.apache.org/jira/browse/RATIS-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885403#comment-16885403 ] Anu Engineer commented on RATIS-606: +1, LGTM. > GrpcService should use SO_REUSEADDR

[jira] [Commented] (RATIS-556) Detect node failures and add other workers to group serving the log and replicate the data of the log

[ https://issues.apache.org/jira/browse/RATIS-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885286#comment-16885286 ] Josh Elser commented on RATIS-556: -- I remember chit-chatting with [~an...@apache.org] abo

[jira] [Commented] (RATIS-541) Add option to verify correctness of batch and mix of batch and single updates data from LogService in VerficiationTool

[ https://issues.apache.org/jira/browse/RATIS-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885263#comment-16885263 ] Josh Elser commented on RATIS-541: -- bq. if the number of records is not divisible by batc

[jira] [Commented] (RATIS-307) Improve make_rc script with additional step of the release process.

[ https://issues.apache.org/jira/browse/RATIS-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885142#comment-16885142 ] Elek, Marton commented on RATIS-307: Sorry for the confusion: I uploaded the new versi

[jira] [Updated] (RATIS-296) Cache entries in the raft log should only be evicted after the entries have successfully been persisted to the Segmented Raft Log

[ https://issues.apache.org/jira/browse/RATIS-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-296: Priority: Blocker (was: Major) > Cache entries in the raft log should only be evicted after

[jira] [Updated] (RATIS-619) Ratis server on restart loads all the entries for the group

[ https://issues.apache.org/jira/browse/RATIS-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-619: Priority: Blocker (was: Major) > Ratis server on restart loads all the entries for the grou

[jira] [Updated] (RATIS-618) Ratis leader should notify stateMachine if the commit index gap between leader and follower is high

[ https://issues.apache.org/jira/browse/RATIS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-618: Priority: Blocker (was: Major) Summary: Ratis leader should notify stateMachine if the

[jira] [Updated] (RATIS-615) StateMachine#notifyExtendedNoLeader is not called when all the nodes in the raft ring are isolated

[ https://issues.apache.org/jira/browse/RATIS-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-615: Priority: Blocker (was: Major) > StateMachine#notifyExtendedNoLeader is not called when all

[jira] [Updated] (RATIS-614) Raft leader should use state machine's last applied index for LeaderNotReady exception

[ https://issues.apache.org/jira/browse/RATIS-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-614: Priority: Blocker (was: Major) > Raft leader should use state machine's last applied index

[jira] [Updated] (RATIS-608) GrpcLogAppender sets next Index erroneously when follower is not accesible.

[ https://issues.apache.org/jira/browse/RATIS-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-608: Priority: Blocker (was: Major) > GrpcLogAppender sets next Index erroneously when follower

[jira] [Updated] (RATIS-570) Ratis generated Exception should not close the channel

[ https://issues.apache.org/jira/browse/RATIS-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-570: Summary: Ratis generated Exception should not close the channel (was: NotLeaderException on

[jira] [Updated] (RATIS-570) NotLeaderException on the server causes the client to close the connection in retryProxy

[ https://issues.apache.org/jira/browse/RATIS-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-570: Priority: Blocker (was: Major) > NotLeaderException on the server causes the client to clos

[jira] [Updated] (RATIS-569) StatusRuntimeException on the datanode because clients do not shutdown the observer cleanly.

[ https://issues.apache.org/jira/browse/RATIS-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-569: Priority: Blocker (was: Major) > StatusRuntimeException on the datanode because clients do

[jira] [Updated] (RATIS-576) NullPointerException at the ratis client while running Freon benchmark

[ https://issues.apache.org/jira/browse/RATIS-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-576: Priority: Blocker (was: Minor) > NullPointerException at the ratis client while running Fre

[jira] [Updated] (RATIS-554) Add metrics related to Quorum heartbeat and statistics on Raft

[ https://issues.apache.org/jira/browse/RATIS-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-554: Priority: Blocker (was: Major) > Add metrics related to Quorum heartbeat and statistics on

[jira] [Updated] (RATIS-562) Add a configurable Purge after Snapshot Policy in Ratis

[ https://issues.apache.org/jira/browse/RATIS-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-562: Priority: Blocker (was: Major) > Add a configurable Purge after Snapshot Policy in Ratis >

[jira] [Updated] (RATIS-543) Ratis GRPC client produces excessive logging while writing data.

[ https://issues.apache.org/jira/browse/RATIS-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-543: Priority: Blocker (was: Major) > Ratis GRPC client produces excessive logging while writing

[jira] [Commented] (RATIS-609) Change RaftLog to use RaftGroupMemberId

[ https://issues.apache.org/jira/browse/RATIS-609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885011#comment-16885011 ] Mukul Kumar Singh commented on RATIS-609: - [~szetszwo], the patch is not applying

[jira] [Commented] (RATIS-541) Add option to verify correctness of batch and mix of batch and single updates data from LogService in VerficiationTool

[ https://issues.apache.org/jira/browse/RATIS-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884909#comment-16884909 ] Rajeshbabu Chintaguntla commented on RATIS-541: --- [~elserj] with v3 version i