You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2019/05/30 08:04:00 UTC
[jira] [Commented] (RATIS-574) Ratis should not use configured
sleep interval in RetryPolicy when it gets LeaderNotException without an
actual Leader election going on
[ https://issues.apache.org/jira/browse/RATIS-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16851616#comment-16851616 ]
Hadoop QA commented on RATIS-574:
---------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s{color} | {color:red} RATIS-574 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/0.8.0/precommit-patchnames for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | RATIS-574 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12970275/RATIS-574.02.patch |
| Console output | https://builds.apache.org/job/PreCommit-RATIS-Build/801/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> Ratis should not use configured sleep interval in RetryPolicy when it gets LeaderNotException without an actual Leader election going on
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: RATIS-574
> URL: https://issues.apache.org/jira/browse/RATIS-574
> Project: Ratis
> Issue Type: Bug
> Reporter: Aravindan Vijayan
> Assignee: Siddharth Wagle
> Priority: Major
> Attachments: RATIS-574.01.patch, RATIS-574.02.patch
>
>
> While doing performance tests with Ozone, it was observed that the client always waits for retry timeout when a NotLeaderException is logged. This bears a performance penalty for the client who cannot try the next Ratis server in the ring.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)