You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Tsz-wo Sze (Jira)" <ji...@apache.org> on 2023/11/30 17:15:00 UTC

[jira] [Updated] (RATIS-1945) INCONSISTENCY replies should be counted as errors.

     [ https://issues.apache.org/jira/browse/RATIS-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsz-wo Sze updated RATIS-1945:
------------------------------
    Description: 
HDDS-9784 reported performance degradation even if the min-wait time (added by RATIS-1793) is set to 1ms. -It may be better to enforce the min-wait time only INCONSISTENCY replies.- (see the update below)

(Update) After checked the code, found that RATIS-1836 added error retry policy. INCONSISTENCY replies should be counted as errors. Then, retry policy will delay the retries and the min-wait time can be set as 0ms in order to avoid performance penalty for the non-error case.

  was:HDDS-9784 reported performance degradation even if the min-wait time (added by RATIS-1793) is set to 1ms.  It may be better to enforce the min-wait time only INCONSISTENCY replies.

        Summary: INCONSISTENCY replies should be counted as errors.  (was: Enforce min wait time only for INCONSISTENCY replies)

> INCONSISTENCY replies should be counted as errors.
> --------------------------------------------------
>
>                 Key: RATIS-1945
>                 URL: https://issues.apache.org/jira/browse/RATIS-1945
>             Project: Ratis
>          Issue Type: Improvement
>          Components: gRPC
>            Reporter: Tsz-wo Sze
>            Assignee: Tsz-wo Sze
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> HDDS-9784 reported performance degradation even if the min-wait time (added by RATIS-1793) is set to 1ms. -It may be better to enforce the min-wait time only INCONSISTENCY replies.- (see the update below)
> (Update) After checked the code, found that RATIS-1836 added error retry policy. INCONSISTENCY replies should be counted as errors. Then, retry policy will delay the retries and the min-wait time can be set as 0ms in order to avoid performance penalty for the non-error case.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)