[jira] [Commented] (RATIS-649) Add metrics related to ClientRequests

[ https://issues.apache.org/jira/browse/RATIS-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954494#comment-16954494 ] Shashikant Banerjee commented on RATIS-649: --- +1 on the change. > Add metrics related to

[jira] [Commented] (RATIS-717) NPE thrown on the follower while instantiating RaftLeaderMetrics

[ https://issues.apache.org/jira/browse/RATIS-717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954473#comment-16954473 ] Shashikant Banerjee commented on RATIS-717: --- Thanks [~avijayan] for working on this. I am +1 on

[jira] [Commented] (RATIS-676) Add a metric in RaftServer to track the Log Commit Index

[ https://issues.apache.org/jira/browse/RATIS-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16954478#comment-16954478 ] Shashikant Banerjee commented on RATIS-676: --- Thanks [~avijayan] for working on this. I am +1 on

[jira] [Created] (RATIS-724) Leader election seem to timeout in Ratis

Shashikant Banerjee created RATIS-724: - Summary: Leader election seem to timeout in Ratis Key: RATIS-724 URL: https://issues.apache.org/jira/browse/RATIS-724 Project: Ratis Issue Type:

[jira] [Updated] (RATIS-726) TimeoutScheduler holds on to the raftClientRequest till it times out even though request succeeds

[ https://issues.apache.org/jira/browse/RATIS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated RATIS-726: -- Description: While running freon with 1 Node ratis, it was observed that the

[jira] [Updated] (RATIS-726) TimeoutScheduler holds on to the raftClientRequest till it times out even though request succeeds

[ https://issues.apache.org/jira/browse/RATIS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated RATIS-726: -- Description: While running freon with 1 Node ratis, it was observed that the

[jira] [Updated] (RATIS-726) TimeoutScheduler holds on to the raftClientRequest till it times out even though request succeeds

[ https://issues.apache.org/jira/browse/RATIS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated RATIS-726: -- Description: While running freon with 1 Node ratis, it was observed that the

[jira] [Created] (RATIS-726) TimeoutScheduler holds on to the raftClientRequest till it times out even though request succeeds

Shashikant Banerjee created RATIS-726: - Summary: TimeoutScheduler holds on to the raftClientRequest till it times out even though request succeeds Key: RATIS-726 URL:

[jira] [Commented] (RATIS-728) TimeoutScheduler for GrpcLogAppender holds on to the AppendEntryRequest till it times out even though request succeeds

[ https://issues.apache.org/jira/browse/RATIS-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16958735#comment-16958735 ] Shashikant Banerjee commented on RATIS-728: --- +1 > TimeoutScheduler for GrpcLogAppender holds on

[jira] [Commented] (RATIS-728) TimeoutScheduler for GrpcLogAppender holds on to the AppendEntryRequest till it times out even though request succeeds

[ https://issues.apache.org/jira/browse/RATIS-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16958736#comment-16958736 ] Shashikant Banerjee commented on RATIS-728: --- Thanks [~szetszwo] for working on this. I have

[jira] [Commented] (RATIS-726) TimeoutScheduler holds on to the raftClientRequest till it times out even though request succeeds

[ https://issues.apache.org/jira/browse/RATIS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957196#comment-16957196 ] Shashikant Banerjee commented on RATIS-726: --- Thanks [~szetszwo] for working on this. I think

[jira] [Assigned] (RATIS-709) RaftClient should not retry on a different leader on NotReplicated exception from leader

[ https://issues.apache.org/jira/browse/RATIS-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned RATIS-709: - Assignee: Shashikant Banerjee > RaftClient should not retry on a different

[jira] [Created] (RATIS-718) Raft client retry request failure

Shashikant Banerjee created RATIS-718: - Summary: Raft client retry request failure Key: RATIS-718 URL: https://issues.apache.org/jira/browse/RATIS-718 Project: Ratis Issue Type: Bug

[jira] [Updated] (RATIS-709) RaftClient should not retry on a different leader on NotReplicated exception from leader

[ https://issues.apache.org/jira/browse/RATIS-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated RATIS-709: -- Description: Currently, when a watch request times out with a NotReplicatedException on

[jira] [Updated] (RATIS-709) RaftClient should not retry on a different leader on NotReplicated exception from leader

[ https://issues.apache.org/jira/browse/RATIS-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated RATIS-709: -- Description: Currently, when a watch request times out with a NotReplicatedException on

[jira] [Commented] (RATIS-676) Add a metric in RaftServer to track the Log Commit Index

[ https://issues.apache.org/jira/browse/RATIS-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953488#comment-16953488 ] Shashikant Banerjee commented on RATIS-676: --- [~avijayan], can you rebase? > Add a metric in

[jira] [Commented] (RATIS-649) Add metrics related to ClientRequests

[ https://issues.apache.org/jira/browse/RATIS-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953487#comment-16953487 ] Shashikant Banerjee commented on RATIS-649: --- [~avijayan], can you rebase?   > Add metrics

[jira] [Created] (RATIS-722) logAppend fails with Timeout exception while reading the stateMachine log entry

Shashikant Banerjee created RATIS-722: - Summary: logAppend fails with Timeout exception while reading the stateMachine log entry Key: RATIS-722 URL: https://issues.apache.org/jira/browse/RATIS-722

[jira] [Created] (RATIS-728) TimeoutScheduler for GrpcLogAppender holds on to the AppendEntryRequest till it times out even though request succeeds

Shashikant Banerjee created RATIS-728: - Summary: TimeoutScheduler for GrpcLogAppender holds on to the AppendEntryRequest till it times out even though request succeeds Key: RATIS-728 URL:

[jira] [Commented] (RATIS-726) TimeoutScheduler holds on to the raftClientRequest till it times out even though request succeeds

[ https://issues.apache.org/jira/browse/RATIS-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957616#comment-16957616 ] Shashikant Banerjee commented on RATIS-726: --- Thanks [~szetszwo]. The changes look good to me. I

[jira] [Assigned] (RATIS-728) TimeoutScheduler for GrpcLogAppender holds on to the AppendEntryRequest till it times out even though request succeeds

[ https://issues.apache.org/jira/browse/RATIS-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned RATIS-728: - Assignee: Tsz-wo Sze > TimeoutScheduler for GrpcLogAppender holds on to the

[jira] [Commented] (RATIS-760) Add missing Grpc log append entries timeout metric

[ https://issues.apache.org/jira/browse/RATIS-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16983341#comment-16983341 ] Shashikant Banerjee commented on RATIS-760: --- patch v1 looks good to me. I am +1 on this. > Add

[jira] [Created] (RATIS-688) Avoid buffer copies while submitting client requests in Ratis

Shashikant Banerjee created RATIS-688: - Summary: Avoid buffer copies while submitting client requests in Ratis Key: RATIS-688 URL: https://issues.apache.org/jira/browse/RATIS-688 Project: Ratis

[jira] [Commented] (RATIS-676) Add a metric in RaftServer to track the Log Commit Index

[ https://issues.apache.org/jira/browse/RATIS-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16945573#comment-16945573 ] Shashikant Banerjee commented on RATIS-676: --- Retriggered the jenkins. > Add a metric in

[jira] [Commented] (RATIS-676) Add a metric in RaftServer to track the Log Commit Index

[ https://issues.apache.org/jira/browse/RATIS-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16948329#comment-16948329 ] Shashikant Banerjee commented on RATIS-676: --- Thanks [~avijayan] for working on this. The logic

[jira] [Commented] (RATIS-676) Add a metric in RaftServer to track the Log Commit Index

[ https://issues.apache.org/jira/browse/RATIS-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16947884#comment-16947884 ] Shashikant Banerjee commented on RATIS-676: --- [~avijayan], can you please rebase the patch? >

[jira] [Created] (RATIS-709) RaftClient should not retry on a different leader on NotReplicated exception from leader

Shashikant Banerjee created RATIS-709: - Summary: RaftClient should not retry on a different leader on NotReplicated exception from leader Key: RATIS-709 URL: https://issues.apache.org/jira/browse/RATIS-709

[jira] [Created] (RATIS-710) GC pauses in leader should not penalize appendRequest response processing

Shashikant Banerjee created RATIS-710: - Summary: GC pauses in leader should not penalize appendRequest response processing Key: RATIS-710 URL: https://issues.apache.org/jira/browse/RATIS-710

[jira] [Created] (RATIS-711) Add ability to specify higher request timeout in watch request

Shashikant Banerjee created RATIS-711: - Summary: Add ability to specify higher request timeout in watch request Key: RATIS-711 URL: https://issues.apache.org/jira/browse/RATIS-711 Project: Ratis

[jira] [Comment Edited] (RATIS-776) Handle ResourceUnavailabeException properly in Ratis Server

[ https://issues.apache.org/jira/browse/RATIS-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000619#comment-17000619 ] Shashikant Banerjee edited comment on RATIS-776 at 12/20/19 5:22 AM: -

[jira] [Commented] (RATIS-776) Handle ResourceUnavailabeException properly in Ratis Server

[ https://issues.apache.org/jira/browse/RATIS-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000619#comment-17000619 ] Shashikant Banerjee commented on RATIS-776: --- Thanks [~ljain] for the updated patch. Can we add

[jira] [Created] (RATIS-785) Statemachine updater fails with assertion

Shashikant Banerjee created RATIS-785: - Summary: Statemachine updater fails with assertion Key: RATIS-785 URL: https://issues.apache.org/jira/browse/RATIS-785 Project: Ratis Issue Type:

[jira] [Created] (RATIS-786) Rename the callId in log Appender to appendId

Shashikant Banerjee created RATIS-786: - Summary: Rename the callId in log Appender to appendId Key: RATIS-786 URL: https://issues.apache.org/jira/browse/RATIS-786 Project: Ratis Issue

[jira] [Created] (RATIS-784) Fix the metric for ratis log sync batch size

Shashikant Banerjee created RATIS-784: - Summary: Fix the metric for ratis log sync batch size Key: RATIS-784 URL: https://issues.apache.org/jira/browse/RATIS-784 Project: Ratis Issue

[jira] [Updated] (RATIS-784) Fix the metric for ratis log sync batch size

[ https://issues.apache.org/jira/browse/RATIS-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated RATIS-784: -- Attachment: RATIS-784.000.patch > Fix the metric for ratis log sync batch size >

[jira] [Updated] (RATIS-784) Fix the metric for ratis log sync batch size

[ https://issues.apache.org/jira/browse/RATIS-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated RATIS-784: -- Attachment: RATIS-778.000.patch > Fix the metric for ratis log sync batch size >

[jira] [Updated] (RATIS-784) Fix the metric for ratis log sync batch size

[ https://issues.apache.org/jira/browse/RATIS-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated RATIS-784: -- Attachment: (was: RATIS-778.000.patch) > Fix the metric for ratis log sync batch

[jira] [Commented] (RATIS-794) Ratils leader should retry append requests based on follower commit info in case of intermittent append failures

[ https://issues.apache.org/jira/browse/RATIS-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022039#comment-17022039 ] Shashikant Banerjee commented on RATIS-794: --- Thanks [~szetszwo] for the patch. The patch needs

[jira] [Created] (RATIS-801) Ratis snapshot should consider stateMachine#appliedIndex for triggering snapshot

Shashikant Banerjee created RATIS-801: - Summary: Ratis snapshot should consider stateMachine#appliedIndex for triggering snapshot Key: RATIS-801 URL: https://issues.apache.org/jira/browse/RATIS-801

[jira] [Commented] (RATIS-795) Read SateMachine data failure should result in log fail notification

[ https://issues.apache.org/jira/browse/RATIS-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17021868#comment-17021868 ] Shashikant Banerjee commented on RATIS-795: --- Thanks [~swagle] for the clarification . I am +1 on

[jira] [Updated] (RATIS-794) Ratils leader should retry append requests based on follower commit info in case of intermittent append failures

[ https://issues.apache.org/jira/browse/RATIS-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated RATIS-794: -- Attachment: (was: RATIS-794.000.patch) > Ratils leader should retry append requests

[jira] [Commented] (RATIS-796) Add watch time out for Ratis Client

[ https://issues.apache.org/jira/browse/RATIS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17021865#comment-17021865 ] Shashikant Banerjee commented on RATIS-796: --- I am +1 on the change. > Add watch time out for

[jira] [Created] (RATIS-803) Add a metric for count of resource limit of pending requests in ratis leader

Shashikant Banerjee created RATIS-803: - Summary: Add a metric for count of resource limit of pending requests in ratis leader Key: RATIS-803 URL: https://issues.apache.org/jira/browse/RATIS-803

[jira] [Commented] (RATIS-683) Test and cleanup Ratis Metrics work

[ https://issues.apache.org/jira/browse/RATIS-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026040#comment-17026040 ] Shashikant Banerjee commented on RATIS-683: --- Thanks [~avijayan] for working on this. The patch

[jira] [Updated] (RATIS-802) Add a metric for Pending request count in Grpc Log Appender

[ https://issues.apache.org/jira/browse/RATIS-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated RATIS-802: -- Summary: Add a metric for Pending request count in Grpc Log Appender (was: Add a

[jira] [Updated] (RATIS-802) Add a metric for Pending request limit hit count in Grpc Log Appender

[ https://issues.apache.org/jira/browse/RATIS-802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated RATIS-802: -- Summary: Add a metric for Pending request limit hit count in Grpc Log Appender (was:

[jira] [Commented] (RATIS-794) Ratils leader should retry append requests based on follower commit info in case of intermittent append failures

[ https://issues.apache.org/jira/browse/RATIS-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031407#comment-17031407 ] Shashikant Banerjee commented on RATIS-794: --- Thanks [~szetszwo] for the patch. I have verified

[jira] [Commented] (RATIS-759) Support stream APIs to send large messages

[ https://issues.apache.org/jira/browse/RATIS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031417#comment-17031417 ] Shashikant Banerjee commented on RATIS-759: --- Thanks [~szetszwo] for updating the patch. The

[jira] [Comment Edited] (RATIS-759) Support stream APIs to send large messages

[ https://issues.apache.org/jira/browse/RATIS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026585#comment-17026585 ] Shashikant Banerjee edited comment on RATIS-759 at 1/31/20 12:27 PM: -

[jira] [Comment Edited] (RATIS-759) Support stream APIs to send large messages

[ https://issues.apache.org/jira/browse/RATIS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026869#comment-17026869 ] Shashikant Banerjee edited comment on RATIS-759 at 1/31/20 12:31 PM: -

[jira] [Commented] (RATIS-803) Add a metric for count of resource limit of pending requests in ratis leader

[ https://issues.apache.org/jira/browse/RATIS-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17027456#comment-17027456 ] Shashikant Banerjee commented on RATIS-803: --- Thanks [~bharat] for working on this. The patch

[jira] [Comment Edited] (RATIS-759) Support stream APIs to send large messages

[ https://issues.apache.org/jira/browse/RATIS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026869#comment-17026869 ] Shashikant Banerjee edited comment on RATIS-759 at 1/30/20 5:45 PM:

[jira] [Comment Edited] (RATIS-759) Support stream APIs to send large messages

[ https://issues.apache.org/jira/browse/RATIS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026869#comment-17026869 ] Shashikant Banerjee edited comment on RATIS-759 at 1/30/20 5:57 PM:

[jira] [Commented] (RATIS-759) Support stream APIs to send large messages

[ https://issues.apache.org/jira/browse/RATIS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026869#comment-17026869 ] Shashikant Banerjee commented on RATIS-759: --- Thanks [~ljain], i think unless the stream is

[jira] [Comment Edited] (RATIS-759) Support stream APIs to send large messages

[ https://issues.apache.org/jira/browse/RATIS-759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026869#comment-17026869 ] Shashikant Banerjee edited comment on RATIS-759 at 1/30/20 5:55 PM:

[jira] [Commented] (RATIS-803) Add a metric for count of resource limit of pending requests in ratis leader

[ https://issues.apache.org/jira/browse/RATIS-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17029727#comment-17029727 ] Shashikant Banerjee commented on RATIS-803: --- Thanks [~bharat] for updating the patch. +1 > Add

[jira] [Commented] (RATIS-803) Add a metric for count of resource limit of pending requests in ratis leader

[ https://issues.apache.org/jira/browse/RATIS-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17025027#comment-17025027 ] Shashikant Banerjee commented on RATIS-803: --- Thanks [~bharat]. The idea of this Jira as we

[jira] [Commented] (RATIS-802) Add a metric for Pending request count in Grpc Log Appender

[ https://issues.apache.org/jira/browse/RATIS-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17025019#comment-17025019 ] Shashikant Banerjee commented on RATIS-802: --- Thanks [~bharat] for working on this. The patch

[jira] [Commented] (RATIS-683) Test and cleanup Ratis Metrics work

[ https://issues.apache.org/jira/browse/RATIS-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17026717#comment-17026717 ] Shashikant Banerjee commented on RATIS-683: --- Thanks [~avijayan] for updating the patch. The

[jira] [Created] (RATIS-794) Ratils leader should retry append requests based on follower commit info in case of intermittent append failures

Shashikant Banerjee created RATIS-794: - Summary: Ratils leader should retry append requests based on follower commit info in case of intermittent append failures Key: RATIS-794 URL:

[jira] [Commented] (RATIS-777) Client should retry on AlreadyClosedException

[ https://issues.apache.org/jira/browse/RATIS-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017034#comment-17017034 ] Shashikant Banerjee commented on RATIS-777: --- Thanks [~ljain] for the explanation. As i mentioned

[jira] [Comment Edited] (RATIS-777) Client should retry on AlreadyClosedException

[ https://issues.apache.org/jira/browse/RATIS-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017034#comment-17017034 ] Shashikant Banerjee edited comment on RATIS-777 at 1/16/20 3:28 PM:

[jira] [Commented] (RATIS-777) Client should retry on AlreadyClosedException

[ https://issues.apache.org/jira/browse/RATIS-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17015159#comment-17015159 ] Shashikant Banerjee commented on RATIS-777: --- [~ljain], If i remember correctly, the idea of

[jira] [Updated] (RATIS-794) Ratils leader should retry append requests based on follower commit info in case of intermittent append failures

[ https://issues.apache.org/jira/browse/RATIS-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated RATIS-794: -- Attachment: RATIS-794.000.patch > Ratils leader should retry append requests based on

[jira] [Commented] (RATIS-795) Read SateMachine data failure should result in log fail notification

[ https://issues.apache.org/jira/browse/RATIS-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17021019#comment-17021019 ] Shashikant Banerjee commented on RATIS-795: --- Thanks [~swagle] for working on this. The patch

[jira] [Commented] (RATIS-796) Add watch time out for Ratis Client

[ https://issues.apache.org/jira/browse/RATIS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17021028#comment-17021028 ] Shashikant Banerjee commented on RATIS-796: --- Thanks [~bharat] for working in this. 

[jira] [Commented] (RATIS-796) Add watch time out for Ratis Client

[ https://issues.apache.org/jira/browse/RATIS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17017380#comment-17017380 ] Shashikant Banerjee commented on RATIS-796: --- Thanks [~bharat] for working on this. The changes

[jira] [Created] (RATIS-790) GrpcLogAppenders on Ratis leader block on each other

Shashikant Banerjee created RATIS-790: - Summary: GrpcLogAppenders on Ratis leader block on each other Key: RATIS-790 URL: https://issues.apache.org/jira/browse/RATIS-790 Project: Ratis

[jira] [Updated] (RATIS-790) GrpcLogAppenders on Ratis leader block on each other

[ https://issues.apache.org/jira/browse/RATIS-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated RATIS-790: -- Description: {code:java}

[jira] [Assigned] (RATIS-785) Statemachine updater fails with assertion

[ https://issues.apache.org/jira/browse/RATIS-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned RATIS-785: - Assignee: Shashikant Banerjee > Statemachine updater fails with assertion >

[jira] [Updated] (RATIS-785) Statemachine updater fails with assertion

[ https://issues.apache.org/jira/browse/RATIS-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated RATIS-785: -- Attachment: RATIS-785.000.patch > Statemachine updater fails with assertion >

[jira] [Commented] (RATIS-813) Add streamAsync(..)

[ https://issues.apache.org/jira/browse/RATIS-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056899#comment-17056899 ] Shashikant Banerjee commented on RATIS-813: --- The changes look good to me. I am +1 on this. >

[jira] [Resolved] (RATIS-646) Add Metrics for Ratis Data pipeline

[ https://issues.apache.org/jira/browse/RATIS-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee resolved RATIS-646. --- Resolution: Fixed > Add Metrics for Ratis Data pipeline >

[jira] [Updated] (RATIS-834) Add metrics for stateMachine cache count and size in bytes

[ https://issues.apache.org/jira/browse/RATIS-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated RATIS-834: -- Parent: (was: RATIS-646) Issue Type: Bug (was: Sub-task) > Add metrics for

[jira] [Commented] (RATIS-832) Add Metrics for retry cache count as well as size in bytes

[ https://issues.apache.org/jira/browse/RATIS-832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083929#comment-17083929 ] Shashikant Banerjee commented on RATIS-832: --- Thanks [~yjxxtd] for the contribution. I have

[jira] [Commented] (RATIS-834) Add metrics for stateMachine cache count and size in bytes

[ https://issues.apache.org/jira/browse/RATIS-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17083914#comment-17083914 ] Shashikant Banerjee commented on RATIS-834: --- Thanks [~yjxxtd]. The metric should be there in

[jira] [Updated] (RATIS-840) Memory leak of LogAppender

[ https://issues.apache.org/jira/browse/RATIS-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated RATIS-840: -- Priority: Critical (was: Major) > Memory leak of LogAppender >

[jira] [Created] (RATIS-867) TestMetaServer#testListLogs

Shashikant Banerjee created RATIS-867: - Summary: TestMetaServer#testListLogs Key: RATIS-867 URL: https://issues.apache.org/jira/browse/RATIS-867 Project: Ratis Issue Type: Sub-task

[jira] [Created] (RATIS-870) Fix TestFileStoreWithGrpc#testFileStore

Shashikant Banerjee created RATIS-870: - Summary: Fix TestFileStoreWithGrpc#testFileStore Key: RATIS-870 URL: https://issues.apache.org/jira/browse/RATIS-870 Project: Ratis Issue Type:

[jira] [Updated] (RATIS-861) Define all third party jar versions in properties in pom.xml

[ https://issues.apache.org/jira/browse/RATIS-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated RATIS-861: -- Description: Currently, many third library dpendencies are hardcoded in the dependency

[jira] [Created] (RATIS-863) Fix Ratis Unit Test Failures

Shashikant Banerjee created RATIS-863: - Summary: Fix Ratis Unit Test Failures Key: RATIS-863 URL: https://issues.apache.org/jira/browse/RATIS-863 Project: Ratis Issue Type: Task

[jira] [Created] (RATIS-868) Fix TestRaftWithSimulatedRpc#testWithLoad

Shashikant Banerjee created RATIS-868: - Summary: Fix TestRaftWithSimulatedRpc#testWithLoad Key: RATIS-868 URL: https://issues.apache.org/jira/browse/RATIS-868 Project: Ratis Issue Type:

[jira] [Created] (RATIS-864) Fix TestRaftStateMachineExceptionWithGrpc#testRetryOnExceptionDuringReplication

Shashikant Banerjee created RATIS-864: - Summary: Fix TestRaftStateMachineExceptionWithGrpc#testRetryOnExceptionDuringReplication Key: RATIS-864 URL: https://issues.apache.org/jira/browse/RATIS-864

[jira] [Created] (RATIS-861) Define all third party jar versions in properties in pom.xml

Shashikant Banerjee created RATIS-861: - Summary: Define all third party jar versions in properties in pom.xml Key: RATIS-861 URL: https://issues.apache.org/jira/browse/RATIS-861 Project: Ratis

[jira] [Created] (RATIS-865) Fix TestRaftWithGrpc#testStateMachineMetrics

Shashikant Banerjee created RATIS-865: - Summary: Fix TestRaftWithGrpc#testStateMachineMetrics Key: RATIS-865 URL: https://issues.apache.org/jira/browse/RATIS-865 Project: Ratis Issue

[jira] [Created] (RATIS-860) Organize log4j dependency in pom.xml

Shashikant Banerjee created RATIS-860: - Summary: Organize log4j dependency in pom.xml Key: RATIS-860 URL: https://issues.apache.org/jira/browse/RATIS-860 Project: Ratis Issue Type: Bug

[jira] [Created] (RATIS-862) Add third party jar versions as properties in pom.xml

Shashikant Banerjee created RATIS-862: - Summary: Add third party jar versions as properties in pom.xml Key: RATIS-862 URL: https://issues.apache.org/jira/browse/RATIS-862 Project: Ratis

[jira] [Updated] (RATIS-860) Organize log4j dependency in pom.xml

[ https://issues.apache.org/jira/browse/RATIS-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated RATIS-860: -- Attachment: RATIS-860.000.patch > Organize log4j dependency in pom.xml >

[jira] [Created] (RATIS-866) Fix TestServerRestartWithSimulatedRpc#testRestartWithCorruptedLogHeader

Shashikant Banerjee created RATIS-866: - Summary: Fix TestServerRestartWithSimulatedRpc#testRestartWithCorruptedLogHeader Key: RATIS-866 URL: https://issues.apache.org/jira/browse/RATIS-866

[jira] [Updated] (RATIS-869) Fix TestServerRestartWithGrpc#testRestartFollower

[ https://issues.apache.org/jira/browse/RATIS-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee updated RATIS-869: -- Summary: Fix TestServerRestartWithGrpc#testRestartFollower (was: Fix ) > Fix

[jira] [Created] (RATIS-869) Fix

Shashikant Banerjee created RATIS-869: - Summary: Fix Key: RATIS-869 URL: https://issues.apache.org/jira/browse/RATIS-869 Project: Ratis Issue Type: Sub-task Reporter:

[jira] [Created] (RATIS-871) Update to latest Ratis Snapshot 0.6.0-490b689-SNAPSHOT

Shashikant Banerjee created RATIS-871: - Summary: Update to latest Ratis Snapshot 0.6.0-490b689-SNAPSHOT Key: RATIS-871 URL: https://issues.apache.org/jira/browse/RATIS-871 Project: Ratis

[jira] [Commented] (RATIS-857) Thread unsafe HashMap in multi thread

[ https://issues.apache.org/jira/browse/RATIS-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087870#comment-17087870 ] Shashikant Banerjee commented on RATIS-857: --- The patch looks good. Waiting for jenkins.. >

[jira] [Commented] (RATIS-853) Unordered Client request should not sleep when NotLeaderException provides leader information

[ https://issues.apache.org/jira/browse/RATIS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087864#comment-17087864 ] Shashikant Banerjee commented on RATIS-853: --- Thanks [~ljain] for working on this. The patch

[jira] [Commented] (RATIS-859) Infinite leader election in ozone

[ https://issues.apache.org/jira/browse/RATIS-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087880#comment-17087880 ] Shashikant Banerjee commented on RATIS-859: --- I think, its  something we might need to handle in

[jira] [Commented] (RATIS-842) GrpcClientProtocolClient uses NotLeaderException event for LeaderNotReadyException

[ https://issues.apache.org/jira/browse/RATIS-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17082189#comment-17082189 ] Shashikant Banerjee commented on RATIS-842: --- Thanks [~ljain] for reporting and working on this.

[jira] [Commented] (RATIS-835) Include exception based attempt count in raft client request

[ https://issues.apache.org/jira/browse/RATIS-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17082203#comment-17082203 ] Shashikant Banerjee commented on RATIS-835: --- [~ljain], thanks for reporting and working on this.

[jira] [Commented] (RATIS-851) Raft Client should not change leader on ResourceUnavailableException

[ https://issues.apache.org/jira/browse/RATIS-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084759#comment-17084759 ] Shashikant Banerjee commented on RATIS-851: --- Thanks [~ljain] for the contribution. I have

[jira] [Commented] (RATIS-851) Raft Client should not change leader on ResourceUnavailableException

[ https://issues.apache.org/jira/browse/RATIS-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084757#comment-17084757 ] Shashikant Banerjee commented on RATIS-851: --- Thanks [~ljain] for working on this. The changes

[jira] [Commented] (RATIS-832) Add Metrics for retry cache count as well as size in bytes

[ https://issues.apache.org/jira/browse/RATIS-832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17076157#comment-17076157 ] Shashikant Banerjee commented on RATIS-832: --- Thanks [~runzhiwang] for working on this. The

<    1   2   3   4   >