[jira] [Updated] (RATIS-137) RaftBasicTests.testBasicAppendEntries may fail

[ https://issues.apache.org/jira/browse/RATIS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-137: -- Attachment: RATIS-137.002.patch > RaftBasicTests.testBasicAppendEntries may fail >

[jira] [Updated] (RATIS-143) RaftClientImpl should have upper bound on async requests

[ https://issues.apache.org/jira/browse/RATIS-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-143: -- Summary: RaftClientImpl should have upper bound on async requests (was: RaftClientImpl should have

[jira] [Updated] (RATIS-156) Implement configuration for client async requests

[ https://issues.apache.org/jira/browse/RATIS-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-156: -- Attachment: RATIS-156.003.patch [~szetszwo], I have uploaded v3 patch to address your comments. >

[jira] [Created] (RATIS-156) Implement configuration for client async requests

Lokesh Jain created RATIS-156: - Summary: Implement configuration for client async requests Key: RATIS-156 URL: https://issues.apache.org/jira/browse/RATIS-156 Project: Ratis Issue Type: Bug

[jira] [Updated] (RATIS-156) Implement configuration for client async requests

[ https://issues.apache.org/jira/browse/RATIS-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-156: -- Attachment: RATIS-156.001.patch > Implement configuration for client async requests >

[jira] [Updated] (RATIS-143) RaftClientImpl should have upper bound on async requests

[ https://issues.apache.org/jira/browse/RATIS-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-143: -- Attachment: RATIS-143.003.patch > RaftClientImpl should have upper bound on async requests >

[jira] [Commented] (RATIS-143) RaftClientImpl should have upper bound on async requests

[ https://issues.apache.org/jira/browse/RATIS-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16264114#comment-16264114 ] Lokesh Jain commented on RATIS-143: --- Thanks for the review [~szetszwo]. v3 patch addresses your comments.

[jira] [Commented] (RATIS-156) Implement configuration for client async requests

[ https://issues.apache.org/jira/browse/RATIS-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16265667#comment-16265667 ] Lokesh Jain commented on RATIS-156: --- Thanks for the review [~szetszwo]. v2 patch addresses your comments.

[jira] [Updated] (RATIS-160) Retry cache should handle leader change after log commit

[ https://issues.apache.org/jira/browse/RATIS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-160: -- Description: This jira is in relation to the below exception seen in the logs. {code:java}

[jira] [Created] (RATIS-175) RaftServerProxy should close server rpc in case instance creation fails

Lokesh Jain created RATIS-175: - Summary: RaftServerProxy should close server rpc in case instance creation fails Key: RATIS-175 URL: https://issues.apache.org/jira/browse/RATIS-175 Project: Ratis

[jira] [Commented] (RATIS-154) Add setter functions for Raft Config keys

[ https://issues.apache.org/jira/browse/RATIS-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16293833#comment-16293833 ] Lokesh Jain commented on RATIS-154: --- [~shashikant] thanks for updating the patch. +1, the v3 patch looks

[jira] [Updated] (RATIS-160) Retry cache should handle leader change after log commit

[ https://issues.apache.org/jira/browse/RATIS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-160: -- Attachment: RATIS-160.002.patch > Retry cache should handle leader change after log commit >

[jira] [Commented] (RATIS-160) Retry cache should handle leader change after log commit

[ https://issues.apache.org/jira/browse/RATIS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292391#comment-16292391 ] Lokesh Jain commented on RATIS-160: --- [~jingzhao], Thanks for the offline discussion! v2 patch refreshes

[jira] [Commented] (RATIS-113) Add Async send interface to RaftClient

[ https://issues.apache.org/jira/browse/RATIS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16247978#comment-16247978 ] Lokesh Jain commented on RATIS-113: --- Thanks for the review [~szetszwo]. v2 patch addresses the comments

[jira] [Updated] (RATIS-113) Add Async send interface to RaftClient

[ https://issues.apache.org/jira/browse/RATIS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-113: -- Attachment: RATIS-113.002.patch > Add Async send interface to RaftClient >

[jira] [Commented] (RATIS-113) Add Async send interface to RaftClient

[ https://issues.apache.org/jira/browse/RATIS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248831#comment-16248831 ] Lokesh Jain commented on RATIS-113: --- I have also changed the logic of

[jira] [Comment Edited] (RATIS-113) Add Async send interface to RaftClient

[ https://issues.apache.org/jira/browse/RATIS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248829#comment-16248829 ] Lokesh Jain edited comment on RATIS-113 at 11/12/17 11:50 AM: -- Thanks for the

[jira] [Commented] (RATIS-113) Add Async send interface to RaftClient

[ https://issues.apache.org/jira/browse/RATIS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248829#comment-16248829 ] Lokesh Jain commented on RATIS-113: --- Thanks for the review [~szetszwo]. v3 patch addresses the above

[jira] [Comment Edited] (RATIS-113) Add Async send interface to RaftClient

[ https://issues.apache.org/jira/browse/RATIS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248829#comment-16248829 ] Lokesh Jain edited comment on RATIS-113 at 11/12/17 11:51 AM: -- Thanks for the

[jira] [Updated] (RATIS-113) Add Async send interface to RaftClient

[ https://issues.apache.org/jira/browse/RATIS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-113: -- Attachment: RATIS-113.003.patch > Add Async send interface to RaftClient >

[jira] [Comment Edited] (RATIS-113) Add Async send interface to RaftClient

[ https://issues.apache.org/jira/browse/RATIS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248829#comment-16248829 ] Lokesh Jain edited comment on RATIS-113 at 11/12/17 11:58 AM: -- Thanks for the

[jira] [Updated] (RATIS-143) RaftClientImpl should have upper bound on async requests

[ https://issues.apache.org/jira/browse/RATIS-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-143: -- Attachment: RATIS-143.002.patch > RaftClientImpl should have upper bound on async requests >

[jira] [Commented] (RATIS-143) RaftClientImpl should have upper bound on async requests

[ https://issues.apache.org/jira/browse/RATIS-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261186#comment-16261186 ] Lokesh Jain commented on RATIS-143: --- [~msingh] [~szetszwo] Thanks for the review! I have uploaded v2

[jira] [Updated] (RATIS-113) Add Async send interface to RaftClient

[ https://issues.apache.org/jira/browse/RATIS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-113: -- Attachment: RATIS-113.004.patch > Add Async send interface to RaftClient >

[jira] [Updated] (RATIS-137) RaftBasicTests.testBasicAppendEntries may fail

[ https://issues.apache.org/jira/browse/RATIS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-137: -- Attachment: RATIS-137.003.patch > RaftBasicTests.testBasicAppendEntries may fail >

[jira] [Commented] (RATIS-137) RaftBasicTests.testBasicAppendEntries may fail

[ https://issues.apache.org/jira/browse/RATIS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248430#comment-16248430 ] Lokesh Jain commented on RATIS-137: --- Thanks for the review [~szetszwo]. v3 patch addresses your comments.

[jira] [Updated] (RATIS-113) Add Async send interface to RaftClient

[ https://issues.apache.org/jira/browse/RATIS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-113: -- Attachment: RATIS-113.001.patch This patch adds async api for RaftClient. Currently async call is

[jira] [Assigned] (RATIS-113) Add Async send interface to RaftClient

[ https://issues.apache.org/jira/browse/RATIS-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain reassigned RATIS-113: - Assignee: Lokesh Jain (was: Mukul Kumar Singh) > Add Async send interface to RaftClient >

[jira] [Updated] (RATIS-137) RaftBasicTests.testBasicAppendEntries may fail

[ https://issues.apache.org/jira/browse/RATIS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-137: -- Attachment: RATIS-137.001.patch > RaftBasicTests.testBasicAppendEntries may fail >

[jira] [Commented] (RATIS-160) Retry cache should handle leader change after log commit

[ https://issues.apache.org/jira/browse/RATIS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16283267#comment-16283267 ] Lokesh Jain commented on RATIS-160: --- The error occurred when I was trying to add testWithLoad for the

[jira] [Created] (RATIS-169) Add TestWithLoad for async api

Lokesh Jain created RATIS-169: - Summary: Add TestWithLoad for async api Key: RATIS-169 URL: https://issues.apache.org/jira/browse/RATIS-169 Project: Ratis Issue Type: Bug Reporter:

[jira] [Comment Edited] (RATIS-160) Retry cache should handle leader change after log commit

[ https://issues.apache.org/jira/browse/RATIS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285503#comment-16285503 ] Lokesh Jain edited comment on RATIS-160 at 12/11/17 4:38 AM: - > The bug happens

[jira] [Commented] (RATIS-160) Retry cache should handle leader change after log commit

[ https://issues.apache.org/jira/browse/RATIS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285454#comment-16285454 ] Lokesh Jain commented on RATIS-160: --- [~jingzhao] thanks for the review! The failed cache entry is in the

[jira] [Commented] (RATIS-160) Retry cache should handle leader change after log commit

[ https://issues.apache.org/jira/browse/RATIS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285477#comment-16285477 ] Lokesh Jain commented on RATIS-160: --- > Do you think the proposed fix in my previous comment can fix the

[jira] [Commented] (RATIS-160) Retry cache should handle leader change after log commit

[ https://issues.apache.org/jira/browse/RATIS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285503#comment-16285503 ] Lokesh Jain commented on RATIS-160: --- > The bug happens actually in the new leader, while it is committing

[jira] [Updated] (RATIS-160) Retry cache should handle leader change after log commit

[ https://issues.apache.org/jira/browse/RATIS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-160: -- Attachment: RATIS-160.001.patch > Retry cache should handle leader change after log commit >

[jira] [Commented] (RATIS-160) Retry cache should handle leader change after log commit

[ https://issues.apache.org/jira/browse/RATIS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16280876#comment-16280876 ] Lokesh Jain commented on RATIS-160: --- v1 patch fixes the issue by adding entryInLog field in CacheEntry

[jira] [Commented] (RATIS-154) Add setter functions for Raft Config keys

[ https://issues.apache.org/jira/browse/RATIS-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16285315#comment-16285315 ] Lokesh Jain commented on RATIS-154: --- Thanks for working on this [~shashikant]. The patch looks good.

[jira] [Commented] (RATIS-236) Use TimeoutScheduler in RaftClientImpl

[ https://issues.apache.org/jira/browse/RATIS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464165#comment-16464165 ] Lokesh Jain commented on RATIS-236: --- [~szetszwo] Thanks for working on this! The patch looks good to me. 

[jira] [Comment Edited] (RATIS-236) Use TimeoutScheduler in RaftClientImpl

[ https://issues.apache.org/jira/browse/RATIS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464165#comment-16464165 ] Lokesh Jain edited comment on RATIS-236 at 5/4/18 5:27 PM: --- [~szetszwo] Thanks

[jira] [Commented] (RATIS-236) Use TimeoutScheduler in RaftClientImpl

[ https://issues.apache.org/jira/browse/RATIS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464190#comment-16464190 ] Lokesh Jain commented on RATIS-236: --- s may become null after execution of s instanceof

[jira] [Commented] (RATIS-236) Use TimeoutScheduler in RaftClientImpl

[ https://issues.apache.org/jira/browse/RATIS-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464198#comment-16464198 ] Lokesh Jain commented on RATIS-236: --- Yes, I agree. Not an issue. +1. > Use TimeoutScheduler in

[jira] [Resolved] (RATIS-245) Include tests for Rest Client in TestVolume, TestBucket and TestKeys

[ https://issues.apache.org/jira/browse/RATIS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain resolved RATIS-245. --- Resolution: Invalid > Include tests for Rest Client in TestVolume, TestBucket and TestKeys >

[jira] [Created] (RATIS-245) Include tests for Rest Client in TestVolume, TestBucket and TestKeys

Lokesh Jain created RATIS-245: - Summary: Include tests for Rest Client in TestVolume, TestBucket and TestKeys Key: RATIS-245 URL: https://issues.apache.org/jira/browse/RATIS-245 Project: Ratis

[jira] [Commented] (RATIS-235) RaftTestUtil.assertLogEntries should check index for async tests.

[ https://issues.apache.org/jira/browse/RATIS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16460763#comment-16460763 ] Lokesh Jain commented on RATIS-235: --- [~szetszwo] Thanks for working on this! The patch looks very good to

[jira] [Commented] (RATIS-177) Raft Leader should not return LeaderNotReady Exception for old completed requests

[ https://issues.apache.org/jira/browse/RATIS-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312485#comment-16312485 ] Lokesh Jain commented on RATIS-177: --- [~szetszwo] thanks for pointing it out! I have uploaded the v2 patch

[jira] [Commented] (RATIS-177) Raft Leader should not return LeaderNotReady Exception for old completed requests

[ https://issues.apache.org/jira/browse/RATIS-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309772#comment-16309772 ] Lokesh Jain commented on RATIS-177: --- | Why it requires (leaderState != null)? I was doubtful about

[jira] [Comment Edited] (RATIS-177) Raft Leader should not return LeaderNotReady Exception for old completed requests

[ https://issues.apache.org/jira/browse/RATIS-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16309772#comment-16309772 ] Lokesh Jain edited comment on RATIS-177 at 1/3/18 3:08 PM: --- | Why it

[jira] [Updated] (RATIS-177) Raft Leader should not return LeaderNotReady Exception for old completed requests

[ https://issues.apache.org/jira/browse/RATIS-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-177: -- Attachment: RATIS-177.001.patch > Raft Leader should not return LeaderNotReady Exception for old

[jira] [Commented] (RATIS-160) Retry cache should handle leader change after log commit

[ https://issues.apache.org/jira/browse/RATIS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16326421#comment-16326421 ] Lokesh Jain commented on RATIS-160: --- [~jingzhao], Can you please take a look at the v2 patch? > Retry

[jira] [Comment Edited] (RATIS-153) Add continuous heartbeats between Ratis servers to avoid unnecessary leader elections

[ https://issues.apache.org/jira/browse/RATIS-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16333557#comment-16333557 ] Lokesh Jain edited comment on RATIS-153 at 1/21/18 3:41 PM: [~msingh] Thanks

[jira] [Commented] (RATIS-153) asyncAppendEntries misses updating followerstate at end of logsync

[ https://issues.apache.org/jira/browse/RATIS-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16333890#comment-16333890 ] Lokesh Jain commented on RATIS-153: --- Thanks for updating the patch [~msingh]! +1 on v2 patch. >

[jira] [Updated] (RATIS-160) Retry cache should handle leader change after log commit

[ https://issues.apache.org/jira/browse/RATIS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-160: -- Attachment: RATIS-160.004.patch > Retry cache should handle leader change after log commit >

[jira] [Created] (RATIS-203) RaftClient request may wait indefinitely for a reply

Lokesh Jain created RATIS-203: - Summary: RaftClient request may wait indefinitely for a reply Key: RATIS-203 URL: https://issues.apache.org/jira/browse/RATIS-203 Project: Ratis Issue Type: Bug

[jira] [Comment Edited] (RATIS-203) RaftClient request may wait indefinitely for a reply

[ https://issues.apache.org/jira/browse/RATIS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16339121#comment-16339121 ] Lokesh Jain edited comment on RATIS-203 at 1/25/18 11:58 AM: - Possible solution

[jira] [Updated] (RATIS-203) RaftClient request may wait indefinitely for a reply

[ https://issues.apache.org/jira/browse/RATIS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-203: -- Attachment: RATIS-203.002.patch > RaftClient request may wait indefinitely for a reply >

[jira] [Updated] (RATIS-203) RaftClient request may wait indefinitely for a reply

[ https://issues.apache.org/jira/browse/RATIS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-203: -- Attachment: (was: RATIS-203.002.patch) > RaftClient request may wait indefinitely for a reply >

[jira] [Updated] (RATIS-201) MiniRaftCluster#getLeader may incorrectly throw IllegalStateException

[ https://issues.apache.org/jira/browse/RATIS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-201: -- Attachment: RATIS-201.001.patch > MiniRaftCluster#getLeader may incorrectly throw IllegalStateException

[jira] [Updated] (RATIS-201) MiniRaftCluster#getLeader may incorrectly throw IllegalStateException

[ https://issues.apache.org/jira/browse/RATIS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-201: -- Attachment: (was: RATIS-201.001.patch) > MiniRaftCluster#getLeader may incorrectly throw

[jira] [Updated] (RATIS-203) RaftClient request may wait indefinitely for a reply

[ https://issues.apache.org/jira/browse/RATIS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-203: -- Attachment: RATIS-203.002.patch > RaftClient request may wait indefinitely for a reply >

[jira] [Updated] (RATIS-203) RaftClient request may wait indefinitely for a reply

[ https://issues.apache.org/jira/browse/RATIS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-203: -- Attachment: RATIS-203.002.patch > RaftClient request may wait indefinitely for a reply >

[jira] [Commented] (RATIS-203) RaftClient request may wait indefinitely for a reply

[ https://issues.apache.org/jira/browse/RATIS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348602#comment-16348602 ] Lokesh Jain commented on RATIS-203: --- v2 patch fixes the test failure in TestSegmentedRaftLog. The other

[jira] [Updated] (RATIS-203) RaftClient request may wait indefinitely for a reply

[ https://issues.apache.org/jira/browse/RATIS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-203: -- Attachment: (was: RATIS-203.002.patch) > RaftClient request may wait indefinitely for a reply >

[jira] [Commented] (RATIS-203) RaftClient request may wait indefinitely for a reply

[ https://issues.apache.org/jira/browse/RATIS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347328#comment-16347328 ] Lokesh Jain commented on RATIS-203: --- v1 patch has a fix for the first scenario. > RaftClient request may

[jira] [Commented] (RATIS-203) RaftClient request may wait indefinitely for a reply

[ https://issues.apache.org/jira/browse/RATIS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16349706#comment-16349706 ] Lokesh Jain commented on RATIS-203: --- I have tried reuploading the patch but it keeps evaluating the v1

[jira] [Updated] (RATIS-203) RaftClient request may wait indefinitely for a reply

[ https://issues.apache.org/jira/browse/RATIS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-203: -- Attachment: RATIS-203.003.patch > RaftClient request may wait indefinitely for a reply >

[jira] [Updated] (RATIS-201) MiniRaftCluster#getLeader may incorrectly throw IllegalStateException

[ https://issues.apache.org/jira/browse/RATIS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-201: -- Attachment: RATIS-201.002.patch > MiniRaftCluster#getLeader may incorrectly throw IllegalStateException

[jira] [Commented] (RATIS-201) MiniRaftCluster#getLeader may incorrectly throw IllegalStateException

[ https://issues.apache.org/jira/browse/RATIS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16352648#comment-16352648 ] Lokesh Jain commented on RATIS-201: --- I saw the IllegalStateException when I was working on

[jira] [Updated] (RATIS-201) MiniRaftCluster#getLeader may incorrectly throw IllegalStateException

[ https://issues.apache.org/jira/browse/RATIS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-201: -- Attachment: RATIS-201.003.patch > MiniRaftCluster#getLeader may incorrectly throw IllegalStateException

[jira] [Commented] (RATIS-201) MiniRaftCluster#getLeader may incorrectly throw IllegalStateException

[ https://issues.apache.org/jira/browse/RATIS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16352806#comment-16352806 ] Lokesh Jain commented on RATIS-201: --- Yes, sorry my bad. > MiniRaftCluster#getLeader may incorrectly

[jira] [Commented] (RATIS-177) Raft Leader should not return LeaderNotReady Exception for old completed requests

[ https://issues.apache.org/jira/browse/RATIS-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16310096#comment-16310096 ] Lokesh Jain commented on RATIS-177: --- cacheEntry.isDone() cannot be used as for failed requests we refresh

[jira] [Commented] (RATIS-285) Ratis State Machine should have an api to inform about loss of a follower/slow follower

[ https://issues.apache.org/jira/browse/RATIS-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16565582#comment-16565582 ] Lokesh Jain commented on RATIS-285: --- [~msingh] Thanks for working on this! Added test in the patch is

[jira] [Updated] (RATIS-287) "URISyntaxException" warning should not print the stacktrace while ozoneFs command-line execution

[ https://issues.apache.org/jira/browse/RATIS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-287: -- Attachment: RATIS-287.001.patch > "URISyntaxException" warning should not print the stacktrace while

[jira] [Commented] (RATIS-287) "URISyntaxException" warning should not print the stacktrace while ozoneFs command-line execution

[ https://issues.apache.org/jira/browse/RATIS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16570525#comment-16570525 ] Lokesh Jain commented on RATIS-287: --- v1 patch addresses the issue of the configuration INFO logs getting

[jira] [Commented] (RATIS-255) Change FinalizeLogSegment to async

[ https://issues.apache.org/jira/browse/RATIS-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579288#comment-16579288 ] Lokesh Jain commented on RATIS-255: --- [~szetszwo] Thanks for working on this! The patch looks good to me.

[jira] [Commented] (RATIS-252) Add API to state machine for determining server role

[ https://issues.apache.org/jira/browse/RATIS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534726#comment-16534726 ] Lokesh Jain commented on RATIS-252: --- [~szetszwo] I think we can avoid the scenario I described by making

[jira] [Commented] (RATIS-252) Add an API for state machine to determining server role

[ https://issues.apache.org/jira/browse/RATIS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538674#comment-16538674 ] Lokesh Jain commented on RATIS-252: --- Thanks [~szetszwo] for updating the patch! r252_20180710.patch

[jira] [Commented] (RATIS-252) Add an API for state machine to determining server role

[ https://issues.apache.org/jira/browse/RATIS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538897#comment-16538897 ] Lokesh Jain commented on RATIS-252: --- RaftServerTestUtil#getRetryEntry can work in this case. We can call 

[jira] [Commented] (RATIS-252) Add an API for state machine to determining server role

[ https://issues.apache.org/jira/browse/RATIS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16539024#comment-16539024 ] Lokesh Jain commented on RATIS-252: --- [~szetszwo] Thanks for the contribution! I have committed this to

[jira] [Commented] (RATIS-252) Add an API for state machine to determining server role

[ https://issues.apache.org/jira/browse/RATIS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16538820#comment-16538820 ] Lokesh Jain commented on RATIS-252: --- We can introduce a boolean variable in SimpleStateMachine4Testing. 

[jira] [Commented] (RATIS-252) Add an API for state machine to determining server role

[ https://issues.apache.org/jira/browse/RATIS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16539013#comment-16539013 ] Lokesh Jain commented on RATIS-252: --- +1 I will commit it shortly. > Add an API for state machine to

[jira] [Commented] (RATIS-252) Add an API for state machine to determining server role

[ https://issues.apache.org/jira/browse/RATIS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16539002#comment-16539002 ] Lokesh Jain commented on RATIS-252: --- [~szetszwo] I agree it might not be worth the effort. > Add an API

[jira] [Commented] (RATIS-252) Add an API for state machine to determining server role

[ https://issues.apache.org/jira/browse/RATIS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16539562#comment-16539562 ] Lokesh Jain commented on RATIS-252: --- I agree [~szetszwo]. Creating a new example is better than

[jira] [Commented] (RATIS-266) Log Exception thrown during applyTransaction & writeStateMachineData

[ https://issues.apache.org/jira/browse/RATIS-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16536724#comment-16536724 ] Lokesh Jain commented on RATIS-266: --- +1 patch looks good to me. I have committed this to master branch. 

[jira] [Resolved] (RATIS-268) Handle committed client requests on leader crash and shutdown

[ https://issues.apache.org/jira/browse/RATIS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain resolved RATIS-268. --- Resolution: Not A Bug > Handle committed client requests on leader crash and shutdown >

[jira] [Commented] (RATIS-268) Handle committed client requests on leader crash and shutdown

[ https://issues.apache.org/jira/browse/RATIS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16536713#comment-16536713 ] Lokesh Jain commented on RATIS-268: --- Thanks for the information [~szetszwo]. We are updating the retry

[jira] [Created] (RATIS-268) Handle committed client requests on leader crash and shutdown

Lokesh Jain created RATIS-268: - Summary: Handle committed client requests on leader crash and shutdown Key: RATIS-268 URL: https://issues.apache.org/jira/browse/RATIS-268 Project: Ratis Issue

[jira] [Commented] (RATIS-268) Handle committed client requests on leader crash and shutdown

[ https://issues.apache.org/jira/browse/RATIS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16536626#comment-16536626 ] Lokesh Jain commented on RATIS-268: --- These entries are created only in the leader which receives the

[jira] [Commented] (RATIS-252) Add API to state machine for determining server role

[ https://issues.apache.org/jira/browse/RATIS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532854#comment-16532854 ] Lokesh Jain commented on RATIS-252: --- [~szetszwo] Thanks for working on this! The patch looks very good

[jira] [Updated] (RATIS-201) MiniRaftCluster#getLeader may incorrectly throw IllegalStateException

[ https://issues.apache.org/jira/browse/RATIS-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-201: -- Description: It can be possible for more than one server to have their role set as LEADER in a ratis

[jira] [Created] (RATIS-214) Add rpc request timeout for Grpc

Lokesh Jain created RATIS-214: - Summary: Add rpc request timeout for Grpc Key: RATIS-214 URL: https://issues.apache.org/jira/browse/RATIS-214 Project: Ratis Issue Type: Task

[jira] [Updated] (RATIS-214) Add rpc request timeout for Grpc

[ https://issues.apache.org/jira/browse/RATIS-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-214: -- Attachment: RATIS-214.001.patch > Add rpc request timeout for Grpc > >

[jira] [Updated] (RATIS-217) Support timeout for append entry requests(GrpcLogAppender)

[ https://issues.apache.org/jira/browse/RATIS-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-217: -- Attachment: (was: RATIS-217.004.patch) > Support timeout for append entry requests(GrpcLogAppender)

[jira] [Updated] (RATIS-217) Support timeout for append entry requests(GrpcLogAppender)

[ https://issues.apache.org/jira/browse/RATIS-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-217: -- Attachment: RATIS-217.005.patch > Support timeout for append entry requests(GrpcLogAppender) >

[jira] [Commented] (RATIS-217) Support timeout for append entry requests(GrpcLogAppender)

[ https://issues.apache.org/jira/browse/RATIS-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16429258#comment-16429258 ] Lokesh Jain commented on RATIS-217: --- [~szetszwo] Thanks for the review! v5 patch addresses your comments.

[jira] [Commented] (RATIS-224) In RpcTimeout, it should shut down the scheduler if there is no tasks

[ https://issues.apache.org/jira/browse/RATIS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16432091#comment-16432091 ] Lokesh Jain commented on RATIS-224: --- +1 on r224_20180410b.patch. > In RpcTimeout, it should shut down

[jira] [Commented] (RATIS-224) In RpcTimeout, it should shut down the scheduler if there is no tasks

[ https://issues.apache.org/jira/browse/RATIS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16431954#comment-16431954 ] Lokesh Jain commented on RATIS-224: --- [~szetszwo] The patch looks very good to me. There is a typo in

[jira] [Commented] (RATIS-217) Support timeout for append entry requests(GrpcLogAppender)

[ https://issues.apache.org/jira/browse/RATIS-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16427304#comment-16427304 ] Lokesh Jain commented on RATIS-217: --- [~szetszwo] Thanks for reviewing the patch! v3 patch addresses your

[jira] [Updated] (RATIS-217) Support timeout for append entry requests(GrpcLogAppender)

[ https://issues.apache.org/jira/browse/RATIS-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-217: -- Attachment: (was: RATIS-217.002.patch) > Support timeout for append entry requests(GrpcLogAppender)

[jira] [Commented] (RATIS-224) In RpcTimeout, it should shut down the scheduler if there is no tasks

[ https://issues.apache.org/jira/browse/RATIS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16433590#comment-16433590 ] Lokesh Jain commented on RATIS-224: --- [~szetszwo] r224_20180411.patch looks good to me. +1 > In

  1   2   3   4   5   6   7   8   >