[jira] [Updated] (RATIS-270) Replication ALL requests should not be replied from retry cache if they are delayed.
[ https://issues.apache.org/jira/browse/RATIS-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated RATIS-270: -- Attachment: r270_20180810b.patch > Replication ALL requests should not be replied from retry cache if they are > delayed. > > > Key: RATIS-270 > URL: https://issues.apache.org/jira/browse/RATIS-270 > Project: Ratis > Issue Type: Bug > Components: server >Reporter: Mukul Kumar Singh >Assignee: Tsz Wo Nicholas Sze >Priority: Major > Labels: ozone > Attachments: r270_20180810b.patch > > > Retry requests are answered from the retry cache when requests have > Replication_ALL semantics. This leads to a case, where the client retries for > a response which is stuck in the delayed replies queue. This new retry is now > answered from the retry cache even though the request has not been completed > on all the nodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RATIS-270) Replication ALL requests should not be replied from retry cache if they are delayed.
[ https://issues.apache.org/jira/browse/RATIS-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated RATIS-270: -- Attachment: (was: r270_20180810.patch) > Replication ALL requests should not be replied from retry cache if they are > delayed. > > > Key: RATIS-270 > URL: https://issues.apache.org/jira/browse/RATIS-270 > Project: Ratis > Issue Type: Bug > Components: server >Reporter: Mukul Kumar Singh >Assignee: Tsz Wo Nicholas Sze >Priority: Major > Labels: ozone > Attachments: r270_20180810b.patch > > > Retry requests are answered from the retry cache when requests have > Replication_ALL semantics. This leads to a case, where the client retries for > a response which is stuck in the delayed replies queue. This new retry is now > answered from the retry cache even though the request has not been completed > on all the nodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RATIS-270) Replication ALL requests should not be replied from retry cache if they are delayed.
[ https://issues.apache.org/jira/browse/RATIS-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated RATIS-270: -- Attachment: (was: r270_20180803.patch) > Replication ALL requests should not be replied from retry cache if they are > delayed. > > > Key: RATIS-270 > URL: https://issues.apache.org/jira/browse/RATIS-270 > Project: Ratis > Issue Type: Bug > Components: server >Reporter: Mukul Kumar Singh >Assignee: Tsz Wo Nicholas Sze >Priority: Major > Labels: ozone > Attachments: r270_20180810.patch > > > Retry requests are answered from the retry cache when requests have > Replication_ALL semantics. This leads to a case, where the client retries for > a response which is stuck in the delayed replies queue. This new retry is now > answered from the retry cache even though the request has not been completed > on all the nodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RATIS-270) Replication ALL requests should not be replied from retry cache if they are delayed.
[ https://issues.apache.org/jira/browse/RATIS-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated RATIS-270: -- Attachment: r270_20180810.patch > Replication ALL requests should not be replied from retry cache if they are > delayed. > > > Key: RATIS-270 > URL: https://issues.apache.org/jira/browse/RATIS-270 > Project: Ratis > Issue Type: Bug > Components: server >Reporter: Mukul Kumar Singh >Assignee: Tsz Wo Nicholas Sze >Priority: Major > Labels: ozone > Attachments: r270_20180810.patch > > > Retry requests are answered from the retry cache when requests have > Replication_ALL semantics. This leads to a case, where the client retries for > a response which is stuck in the delayed replies queue. This new retry is now > answered from the retry cache even though the request has not been completed > on all the nodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RATIS-270) Replication ALL requests should not be replied from retry cache if they are delayed.
[ https://issues.apache.org/jira/browse/RATIS-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo Nicholas Sze updated RATIS-270: -- Summary: Replication ALL requests should not be replied from retry cache if they are delayed. (was: Replication_ALL requests should not be replied from retry cache if they are present in delayedReplies queue.) > Replication ALL requests should not be replied from retry cache if they are > delayed. > > > Key: RATIS-270 > URL: https://issues.apache.org/jira/browse/RATIS-270 > Project: Ratis > Issue Type: Bug > Components: server >Reporter: Mukul Kumar Singh >Assignee: Tsz Wo Nicholas Sze >Priority: Major > Labels: ozone > Attachments: r270_20180803.patch > > > Retry requests are answered from the retry cache when requests have > Replication_ALL semantics. This leads to a case, where the client retries for > a response which is stuck in the delayed replies queue. This new retry is now > answered from the retry cache even though the request has not been completed > on all the nodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
