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

Mukul Kumar Singh created RATIS-113: --- Summary: Add Async send interface to RaftClient Key: RATIS-113 URL: https://issues.apache.org/jira/browse/RATIS-113 Project: Ratis Issue Type: Bug

[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=16253952#comment-16253952 ] Mukul Kumar Singh commented on RATIS-143: - Thanks for the patch [~ljain], The patch looks good,

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

Mukul Kumar Singh created RATIS-154: --- Summary: Add setter functions for Raft Config keys Key: RATIS-154 URL: https://issues.apache.org/jira/browse/RATIS-154 Project: Ratis Issue Type: Bug

[jira] [Updated] (RATIS-161) gRPC Log appender should check if the appended request size is less than max message size of the server

[ https://issues.apache.org/jira/browse/RATIS-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-161: Attachment: RATIS-161.001.patch > gRPC Log appender should check if the appended request

[jira] [Commented] (RATIS-172) TestBatchAppend fails with timeout

[ https://issues.apache.org/jira/browse/RATIS-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16292101#comment-16292101 ] Mukul Kumar Singh commented on RATIS-172: - TestBatchAppend fails because of the following change.

[jira] [Updated] (RATIS-172) TestBatchAppend fails with timeout

[ https://issues.apache.org/jira/browse/RATIS-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-172: Attachment: RATIS-172.001.patch Thanks for the comment [~szetszwo]. The problem with the

[jira] [Updated] (RATIS-168) Update Grpc version in Ratis.

[ https://issues.apache.org/jira/browse/RATIS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-168: Attachment: RATIS-168.003.patch Thanks for the review [~szetszwo]. I had made changes in the

[jira] [Updated] (RATIS-133) Raft gRPC client should check proto size before sending a message

[ https://issues.apache.org/jira/browse/RATIS-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-133: Attachment: RATIS-133.001.patch > Raft gRPC client should check proto size before sending a

[jira] [Created] (RATIS-146) Maven install should install Proto files as well

Mukul Kumar Singh created RATIS-146: --- Summary: Maven install should install Proto files as well Key: RATIS-146 URL: https://issues.apache.org/jira/browse/RATIS-146 Project: Ratis Issue

[jira] [Updated] (RATIS-146) Maven install should install Proto files as well

[ https://issues.apache.org/jira/browse/RATIS-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-146: Attachment: RATIS-146.001.patch > Maven install should install Proto files as well >

[jira] [Created] (RATIS-152) Fix jmx registration warning in Ozone unit tests.

Mukul Kumar Singh created RATIS-152: --- Summary: Fix jmx registration warning in Ozone unit tests. Key: RATIS-152 URL: https://issues.apache.org/jira/browse/RATIS-152 Project: Ratis Issue

[jira] [Commented] (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=16261092#comment-16261092 ] Mukul Kumar Singh commented on RATIS-153: - The problem seems to be in

[jira] [Commented] (RATIS-6) Project logo

[ https://issues.apache.org/jira/browse/RATIS-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261040#comment-16261040 ] Mukul Kumar Singh commented on RATIS-6: --- +1 > Project logo > > > Key:

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

Mukul Kumar Singh created RATIS-153: --- Summary: Add continuous heartbeats between Ratis servers to avoid unnecessary leader elections Key: RATIS-153 URL: https://issues.apache.org/jira/browse/RATIS-153

[jira] [Commented] (RATIS-133) Raft gRPC client should check proto size before sending a message

[ https://issues.apache.org/jira/browse/RATIS-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16248273#comment-16248273 ] Mukul Kumar Singh commented on RATIS-133: - Thanks for review [~jingzhao]. I did see the config to

[jira] [Created] (RATIS-133) Raft gRPC client should check proto size before sending a message

Mukul Kumar Singh created RATIS-133: --- Summary: Raft gRPC client should check proto size before sending a message Key: RATIS-133 URL: https://issues.apache.org/jira/browse/RATIS-133 Project: Ratis

[jira] [Created] (RATIS-134) PeerProxyMap#addPeers should add peers only if it is not already present in the proxymap

Mukul Kumar Singh created RATIS-134: --- Summary: PeerProxyMap#addPeers should add peers only if it is not already present in the proxymap Key: RATIS-134 URL: https://issues.apache.org/jira/browse/RATIS-134

[jira] [Updated] (RATIS-134) PeerProxyMap#addPeers should add peers only if it is not already present in the proxymap

[ https://issues.apache.org/jira/browse/RATIS-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-134: Attachment: RATIS-134.001.patch > PeerProxyMap#addPeers should add peers only if it is not

[jira] [Created] (RATIS-135) Closed segments contribute to leaked memory as eviction policies are not honoured

Mukul Kumar Singh created RATIS-135: --- Summary: Closed segments contribute to leaked memory as eviction policies are not honoured Key: RATIS-135 URL: https://issues.apache.org/jira/browse/RATIS-135

[jira] [Updated] (RATIS-135) Closed segments contribute to leaked memory as eviction policies are not honoured

[ https://issues.apache.org/jira/browse/RATIS-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-135: Attachment: RATIS-135.001.patch > Closed segments contribute to leaked memory as eviction

[jira] [Updated] (RATIS-135) Closed segments contribute to leaked memory as eviction policies are not honoured

[ https://issues.apache.org/jira/browse/RATIS-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-135: Attachment: RATIS-135.002.patch patch v2 fixes the unit test failure. > Closed segments

[jira] [Updated] (RATIS-136) Reduce log level for segment rollover

[ https://issues.apache.org/jira/browse/RATIS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-136: Attachment: RATIS-136.002.patch > Reduce log level for segment rollover >

[jira] [Updated] (RATIS-134) PeerProxyMap#addPeers should add peers only if it is not already present in the proxymap

[ https://issues.apache.org/jira/browse/RATIS-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-134: Attachment: RATIS-134.002.patch > PeerProxyMap#addPeers should add peers only if it is not

[jira] [Created] (RATIS-136) Reduce log level for segment rollover

Mukul Kumar Singh created RATIS-136: --- Summary: Reduce log level for segment rollover Key: RATIS-136 URL: https://issues.apache.org/jira/browse/RATIS-136 Project: Ratis Issue Type: Bug

[jira] [Updated] (RATIS-136) Reduce log level for segment rollover

[ https://issues.apache.org/jira/browse/RATIS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-136: Attachment: RATIS-136.001.patch > Reduce log level for segment rollover >

[jira] [Updated] (RATIS-168) Update Grpc version in Ratis.

[ https://issues.apache.org/jira/browse/RATIS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-168: Attachment: RATIS-168.001.patch The attached patch updates the Grpc version to 1.5.0.

[jira] [Updated] (RATIS-161) gRPC Log appender should check if the appended request size is less than max message size of the server

[ https://issues.apache.org/jira/browse/RATIS-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-161: Attachment: RATIS-161.002.patch > gRPC Log appender should check if the appended request

[jira] [Commented] (RATIS-161) gRPC Log appender should check if the appended request size is less than max message size of the server

[ https://issues.apache.org/jira/browse/RATIS-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284646#comment-16284646 ] Mukul Kumar Singh commented on RATIS-161: - Hi [~szetszwo], the buffer size is being set as

[jira] [Commented] (RATIS-161) gRPC Log appender should check if the appended request size is less than max message size of the server

[ https://issues.apache.org/jira/browse/RATIS-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16284589#comment-16284589 ] Mukul Kumar Singh commented on RATIS-161: - Hi [~szetszwo], v2 patch fixes this issue by limiting

[jira] [Created] (RATIS-168) Update Grpc version in Ratis.

Mukul Kumar Singh created RATIS-168: --- Summary: Update Grpc version in Ratis. Key: RATIS-168 URL: https://issues.apache.org/jira/browse/RATIS-168 Project: Ratis Issue Type: Bug

[jira] [Updated] (RATIS-168) Update Grpc version in Ratis.

[ https://issues.apache.org/jira/browse/RATIS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-168: Attachment: RATIS-168.002.patch Thanks for the review [~szetszwo], the v2 patch updates the

[jira] [Updated] (RATIS-161) gRPC Log appender should check if the appended request size is less than max message size of the server

[ https://issues.apache.org/jira/browse/RATIS-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-161: Attachment: RATIS-161.003.patch Thanks for the review [~szetszwo], Patch v3 fixes the review

[jira] [Commented] (RATIS-239) LogAppender should reconnect for some IOException

[ https://issues.apache.org/jira/browse/RATIS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16490236#comment-16490236 ] Mukul Kumar Singh commented on RATIS-239: - Thanks for working on this [~szetszwo]. The patch looks

[jira] [Created] (RATIS-246) Support secure gRPC endpoint with mTLS in Ratis

Mukul Kumar Singh created RATIS-246: --- Summary: Support secure gRPC endpoint with mTLS in Ratis Key: RATIS-246 URL: https://issues.apache.org/jira/browse/RATIS-246 Project: Ratis Issue

[jira] [Created] (RATIS-253) Segmented Raft log rolls over segment frequently

Mukul Kumar Singh created RATIS-253: --- Summary: Segmented Raft log rolls over segment frequently Key: RATIS-253 URL: https://issues.apache.org/jira/browse/RATIS-253 Project: Ratis Issue

[jira] [Created] (RATIS-256) Add a cli example for FileStoreStateMachine

Mukul Kumar Singh created RATIS-256: --- Summary: Add a cli example for FileStoreStateMachine Key: RATIS-256 URL: https://issues.apache.org/jira/browse/RATIS-256 Project: Ratis Issue Type:

[jira] [Commented] (RATIS-239) LogAppender should reconnect for some IOException

[ https://issues.apache.org/jira/browse/RATIS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16496205#comment-16496205 ] Mukul Kumar Singh commented on RATIS-239: - Thanks for the updated patch [~szetszwo]. The updated

[jira] [Created] (RATIS-260) Ratis Leader election should try for other peers even when ask for votes fails

Mukul Kumar Singh created RATIS-260: --- Summary: Ratis Leader election should try for other peers even when ask for votes fails Key: RATIS-260 URL: https://issues.apache.org/jira/browse/RATIS-260

[jira] [Commented] (RATIS-231) Grpc server should reconnect if there is an exception

[ https://issues.apache.org/jira/browse/RATIS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16453483#comment-16453483 ] Mukul Kumar Singh commented on RATIS-231: - Thanks for working on this patch [~szetszwo]. The patch

[jira] [Commented] (RATIS-231) Grpc server should reconnect if there is an exception

[ https://issues.apache.org/jira/browse/RATIS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458753#comment-16458753 ] Mukul Kumar Singh commented on RATIS-231: - Thanks for the updated patch [~szetszwo]. The patch

[jira] [Created] (RATIS-186) Add a Config option to specify the flow control window size in Ratis

Mukul Kumar Singh created RATIS-186: --- Summary: Add a Config option to specify the flow control window size in Ratis Key: RATIS-186 URL: https://issues.apache.org/jira/browse/RATIS-186 Project:

[jira] [Updated] (RATIS-186) Add a Config option to specify the flow control window size in Ratis

[ https://issues.apache.org/jira/browse/RATIS-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-186: Attachment: RATIS-186.001.patch > Add a Config option to specify the flow control window

[jira] [Updated] (RATIS-183) In gRPC, Follower should not wait for log sync to process next appendEntries

[ https://issues.apache.org/jira/browse/RATIS-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-183: Attachment: RATIS-183.002.patch Thanks for the quick review [~szetszwo], patch v2 addresses

[jira] [Resolved] (RATIS-182) Leader should wait for the log entries to be appended and synced

[ https://issues.apache.org/jira/browse/RATIS-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh resolved RATIS-182. - Resolution: Not A Problem Thanks for the explanation [~szetszwo], I understand the

[jira] [Updated] (RATIS-189) AppendRequestStreamObserver close can be called twice

[ https://issues.apache.org/jira/browse/RATIS-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-189: Attachment: RATIS-189.002.patch Thanks for the review [~szetszwo], please have a look at the

[jira] [Updated] (RATIS-193) RaftClientProtocolService can close a stream twice on error

[ https://issues.apache.org/jira/browse/RATIS-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-193: Attachment: RATIS-193.001.patch > RaftClientProtocolService can close a stream twice on

[jira] [Updated] (RATIS-196) RaftServerProtocolService may continue to reply after

[ https://issues.apache.org/jira/browse/RATIS-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-196: Attachment: RATIS-196.001.patch > RaftServerProtocolService may continue to reply after >

[jira] [Created] (RATIS-196) RaftServerProtocolService may continue to reply after

Mukul Kumar Singh created RATIS-196: --- Summary: RaftServerProtocolService may continue to reply after Key: RATIS-196 URL: https://issues.apache.org/jira/browse/RATIS-196 Project: Ratis

[jira] [Updated] (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:all-tabpanel ] Mukul Kumar Singh updated RATIS-153: Attachment: RATIS-153.001.patch > Add continuous heartbeats between Ratis servers to avoid

[jira] [Commented] (RATIS-193) RaftClientProtocolService can close a stream twice on error

[ https://issues.apache.org/jira/browse/RATIS-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332017#comment-16332017 ] Mukul Kumar Singh commented on RATIS-193: - Thanks for noticing that [~szetszwo], done I have added

[jira] [Commented] (RATIS-192) TestFileStoreWithGrpc is failing

[ https://issues.apache.org/jira/browse/RATIS-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16332031#comment-16332031 ] Mukul Kumar Singh commented on RATIS-192: - Hi [~szetszwo], The idea looks good to me, I have

[jira] [Updated] (RATIS-192) TestFileStoreWithGrpc is failing

[ https://issues.apache.org/jira/browse/RATIS-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-192: Attachment: RATIS-192.002.patch > TestFileStoreWithGrpc is failing >

[jira] [Updated] (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:all-tabpanel ] Mukul Kumar Singh updated RATIS-153: Attachment: (was: RATIS-153.002.patch) > asyncAppendEntries misses updating

[jira] [Updated] (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:all-tabpanel ] Mukul Kumar Singh updated RATIS-153: Attachment: RATIS-153.002.patch > asyncAppendEntries misses updating followerstate at end of

[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=16333838#comment-16333838 ] Mukul Kumar Singh commented on RATIS-153: - Thanks for the review [~ljain] and [~szetszwo]. I have

[jira] [Updated] (RATIS-196) RaftServerProtocolService may continue to reply after it is closed

[ https://issues.apache.org/jira/browse/RATIS-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-196: Summary: RaftServerProtocolService may continue to reply after it is closed (was:

[jira] [Created] (RATIS-197) Reads are failing in Ozone for keys of size greater than 4MB

Mukul Kumar Singh created RATIS-197: --- Summary: Reads are failing in Ozone for keys of size greater than 4MB Key: RATIS-197 URL: https://issues.apache.org/jira/browse/RATIS-197 Project: Ratis

[jira] [Assigned] (RATIS-191) Support SO_REUSEADDR to avoid netty server bind failure

[ https://issues.apache.org/jira/browse/RATIS-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh reassigned RATIS-191: --- Assignee: Shashikant Banerjee (was: Mukul Kumar Singh) > Support SO_REUSEADDR to

[jira] [Commented] (RATIS-184) Document how to deploy the snapshot artifacts

[ https://issues.apache.org/jira/browse/RATIS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16342931#comment-16342931 ] Mukul Kumar Singh commented on RATIS-184: - Thanks for updating the patch [~szetszwo], the latest

[jira] [Commented] (RATIS-184) Document how to deploy the snapshot artifacts

[ https://issues.apache.org/jira/browse/RATIS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343346#comment-16343346 ] Mukul Kumar Singh commented on RATIS-184: - [~szetszwo] I have committed this change. however I

[jira] [Commented] (RATIS-204) Add getLastAppliedTermIndex to StateMachine

[ https://issues.apache.org/jira/browse/RATIS-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16346995#comment-16346995 ] Mukul Kumar Singh commented on RATIS-204: - Thanks for the patch [~szetszwo], The patch looks good

[jira] [Commented] (RATIS-204) Add getLastAppliedTermIndex to StateMachine

[ https://issues.apache.org/jira/browse/RATIS-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16348023#comment-16348023 ] Mukul Kumar Singh commented on RATIS-204: - Thanks for the update patch [~szetszwo]. patch

[jira] [Commented] (RATIS-197) Reads are failing in Ozone for keys of size greater than 4MB

[ https://issues.apache.org/jira/browse/RATIS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355802#comment-16355802 ] Mukul Kumar Singh commented on RATIS-197: - Added some debug logging and determined that the reads

[jira] [Updated] (RATIS-197) Reads are failing in Ozone for keys of size greater than 4MB

[ https://issues.apache.org/jira/browse/RATIS-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-197: Attachment: RATIS-197.001.patch > Reads are failing in Ozone for keys of size greater than

[jira] [Commented] (RATIS-205) Return commit information to client

[ https://issues.apache.org/jira/browse/RATIS-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361974#comment-16361974 ] Mukul Kumar Singh commented on RATIS-205: - Thanks for updating the patch [~szetszwo], the latest

[jira] [Created] (RATIS-209) StateMachine updater may miss writeLog Request after a new Leader is chosen.

Mukul Kumar Singh created RATIS-209: --- Summary: StateMachine updater may miss writeLog Request after a new Leader is chosen. Key: RATIS-209 URL: https://issues.apache.org/jira/browse/RATIS-209

[jira] [Commented] (RATIS-205) Return commit information to client

[ https://issues.apache.org/jira/browse/RATIS-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363573#comment-16363573 ] Mukul Kumar Singh commented on RATIS-205: - +1, the latest patch looks good to me. > Return commit

[jira] [Commented] (RATIS-205) Return commit information to client

[ https://issues.apache.org/jira/browse/RATIS-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16364392#comment-16364392 ] Mukul Kumar Singh commented on RATIS-205: - Thanks for updating the patch [~szetszwo], the latest

[jira] [Commented] (RATIS-207) Implement stale read

[ https://issues.apache.org/jira/browse/RATIS-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16367323#comment-16367323 ] Mukul Kumar Singh commented on RATIS-207: - Thanks for working on this [~szetszwo]. I patch looks

[jira] [Commented] (RATIS-207) Implement stale read

[ https://issues.apache.org/jira/browse/RATIS-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368548#comment-16368548 ] Mukul Kumar Singh commented on RATIS-207: - Thanks for updating the patch [~szetszwo]. +1, the

[jira] [Updated] (RATIS-168) Update Grpc and netty versions in Ratis.

[ https://issues.apache.org/jira/browse/RATIS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-168: Attachment: RATIS-168.004.patch > Update Grpc and netty versions in Ratis. >

[jira] [Created] (RATIS-182) Leader should wait for the log entries to be appended and synced

Mukul Kumar Singh created RATIS-182: --- Summary: Leader should wait for the log entries to be appended and synced Key: RATIS-182 URL: https://issues.apache.org/jira/browse/RATIS-182 Project: Ratis

[jira] [Created] (RATIS-183) Parallelize log sync in Follower

Mukul Kumar Singh created RATIS-183: --- Summary: Parallelize log sync in Follower Key: RATIS-183 URL: https://issues.apache.org/jira/browse/RATIS-183 Project: Ratis Issue Type: Bug

[jira] [Updated] (RATIS-289) Optimize readStateMachine by allowing to enqueue multiple read requests in parallel

[ https://issues.apache.org/jira/browse/RATIS-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-289: Attachment: (was: RATIS-289.001.patch) > Optimize readStateMachine by allowing to

[jira] [Commented] (RATIS-289) Optimize readStateMachine by allowing to enqueue multiple read requests in parallel

[ https://issues.apache.org/jira/browse/RATIS-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16567840#comment-16567840 ] Mukul Kumar Singh commented on RATIS-289: - Thanks for the review [~szetszwo]. I have addressed the

[jira] [Updated] (RATIS-289) Optimize readStateMachine by allowing to enqueue multiple read requests in parallel

[ https://issues.apache.org/jira/browse/RATIS-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-289: Attachment: RATIS-289.002.patch > Optimize readStateMachine by allowing to enqueue multiple

[jira] [Assigned] (RATIS-260) Ratis Leader election should try for other peers even when ask for votes fails

[ https://issues.apache.org/jira/browse/RATIS-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh reassigned RATIS-260: --- Assignee: Shashikant Banerjee (was: Nanda kumar) > Ratis Leader election should try

[jira] [Updated] (RATIS-286) Add information about raft peers and rpc delay in ServerInformationReply

[ https://issues.apache.org/jira/browse/RATIS-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-286: Summary: Add information about raft peers and rpc delay in ServerInformationReply (was:

[jira] [Updated] (RATIS-286) Add information about ratft peers and rpc deplay in ServerInformationReply

[ https://issues.apache.org/jira/browse/RATIS-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-286: Attachment: RATIS-286.001.patch > Add information about ratft peers and rpc deplay in

[jira] [Commented] (RATIS-281) Ratis should provide an api to readStateMachinedata when the cached segment is not available

[ https://issues.apache.org/jira/browse/RATIS-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16561006#comment-16561006 ] Mukul Kumar Singh commented on RATIS-281: - Thanks for the review [~szetszwo]. I have addressed the

[jira] [Updated] (RATIS-281) Ratis should provide an api to readStateMachinedata when the cached segment is not available

[ https://issues.apache.org/jira/browse/RATIS-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-281: Attachment: (was: RATIS-281.002.patch) > Ratis should provide an api to

[jira] [Updated] (RATIS-281) Ratis should provide an api to readStateMachinedata when the cached segment is not available

[ https://issues.apache.org/jira/browse/RATIS-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-281: Attachment: (was: RATIS-281.001.patch) > Ratis should provide an api to

[jira] [Updated] (RATIS-281) Ratis should provide an api to readStateMachinedata when the cached segment is not available

[ https://issues.apache.org/jira/browse/RATIS-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-281: Attachment: RATIS-281.003.patch > Ratis should provide an api to readStateMachinedata when

[jira] [Created] (RATIS-286) Add information about ratft peers and rpc deplay in ServerInformationReply

Mukul Kumar Singh created RATIS-286: --- Summary: Add information about ratft peers and rpc deplay in ServerInformationReply Key: RATIS-286 URL: https://issues.apache.org/jira/browse/RATIS-286

[jira] [Updated] (RATIS-286) Add information about raft peers and rpc deplay in ServerInformationReply

[ https://issues.apache.org/jira/browse/RATIS-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-286: Summary: Add information about raft peers and rpc deplay in ServerInformationReply (was:

[jira] [Created] (RATIS-281) Ratis should provide an api to readStateMachinedata when the cached segment is not available

Mukul Kumar Singh created RATIS-281: --- Summary: Ratis should provide an api to readStateMachinedata when the cached segment is not available Key: RATIS-281 URL: https://issues.apache.org/jira/browse/RATIS-281

[jira] [Created] (RATIS-284) FollowerInfo#toString should pring the elapsed time from last rpc

Mukul Kumar Singh created RATIS-284: --- Summary: FollowerInfo#toString should pring the elapsed time from last rpc Key: RATIS-284 URL: https://issues.apache.org/jira/browse/RATIS-284 Project: Ratis

[jira] [Updated] (RATIS-284) FollowerInfo#toString should pring the elapsed time from last rpc

[ https://issues.apache.org/jira/browse/RATIS-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-284: Attachment: RATIS-284.001.patch > FollowerInfo#toString should pring the elapsed time from

[jira] [Created] (RATIS-270) Replication_ALL requests should not be replied from retry cache if they are present in delayedReplies queue.

Mukul Kumar Singh created RATIS-270: --- Summary: Replication_ALL requests should not be replied from retry cache if they are present in delayedReplies queue. Key: RATIS-270 URL:

[jira] [Updated] (RATIS-167) Implement a high performance OutputStream using async API

[ https://issues.apache.org/jira/browse/RATIS-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-167: Labels: ozone (was: oz) > Implement a high performance OutputStream using async API >

[jira] [Updated] (RATIS-267) Add a unique identifier for a ratis ring during initialization/add peers to identify a unique ratis ring

[ https://issues.apache.org/jira/browse/RATIS-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-267: Labels: ozone (was: ) > Add a unique identifier for a ratis ring during initialization/add

[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 ] Mukul Kumar Singh updated RATIS-287: Labels: ozone (was: ) > "URISyntaxException" warning should not print the stacktrace while

[jira] [Updated] (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:all-tabpanel ] Mukul Kumar Singh updated RATIS-285: Labels: ozone (was: ) > Ratis State Machine should have an api to inform about loss of a

[jira] [Updated] (RATIS-91) Add multi-raft support

[ https://issues.apache.org/jira/browse/RATIS-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-91: --- Labels: ozone (was: ) > Add multi-raft support > -- > >

[jira] [Updated] (RATIS-198) Ozone Ratis test is failing with Socket IO exception during Key Creation

[ https://issues.apache.org/jira/browse/RATIS-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-198: Labels: ozone (was: ) > Ozone Ratis test is failing with Socket IO exception during Key

[jira] [Updated] (RATIS-167) Implement a high performance OutputStream using async API

[ https://issues.apache.org/jira/browse/RATIS-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-167: Labels: oz (was: ) > Implement a high performance OutputStream using async API >

[jira] [Updated] (RATIS-188) SlidingWindow should be able to limit the window size

[ https://issues.apache.org/jira/browse/RATIS-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-188: Labels: ozone (was: ) > SlidingWindow should be able to limit the window size >

[jira] [Updated] (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:all-tabpanel ] Mukul Kumar Singh updated RATIS-285: Attachment: (was: RATIS-285.001.patch) > Ratis State Machine should have an api to

[jira] [Updated] (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:all-tabpanel ] Mukul Kumar Singh updated RATIS-285: Attachment: RATIS-285.003.patch > Ratis State Machine should have an api to inform about

[jira] [Updated] (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:all-tabpanel ] Mukul Kumar Singh updated RATIS-285: Attachment: (was: RATIS-285.002.patch) > Ratis State Machine should have an api to

  1   2   3   4   5   6   7   >