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 Nicholas Sze (JIRA)" <ji...@apache.org> on 2018/09/10 17:25:00 UTC
[jira] [Commented] (RATIS-313) Raft client ignores the
reinitilization exception when the raft server is not ready
[ https://issues.apache.org/jira/browse/RATIS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16609535#comment-16609535 ]
Tsz Wo Nicholas Sze commented on RATIS-313:
-------------------------------------------
The reinitialize API is going to be replaced in RATIS-305. Please don't change anything for the moment.
> Raft client ignores the reinitilization exception when the raft server is not ready
> -----------------------------------------------------------------------------------
>
> Key: RATIS-313
> URL: https://issues.apache.org/jira/browse/RATIS-313
> Project: Ratis
> Issue Type: Bug
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Major
>
> This was found in Ozone testing.
> Three nodes in the pipeline.
> {code:java}
> group-2041ABBEE452:[bfe9c5f2-da9b-4a8f-9013-7540cbbed1c9:172.27.12.96:9858, faa888b7-92bb-4e35-a38c-711bd1c28948:172.27.80.23:9858, ff544de8-96ea-4097-8cdc-460ac1c60db7:172.27.23.161:9858]
> {code}
> On two servers, the reinitialization request succeeds,
> {code:java}
> 2018-09-09 10:49:40,938 INFO org.apache.ratis.server.impl.RaftServerProxy: faa888b7-92bb-4e35-a38c-711bd1c28948: reinitializeAsync ReinitializeRequest(client-682DF1D0F737->faa888b7-92bb-4e35-a38c-711bd1c28948) in group-7347726F7570, cid=4, seq=0 RW, null, group-2041ABBEE452:[bfe9c5f2-da9b-4a8f-9013-7540cbbed1c9:172.27.12.96:9858, faa888b7-92bb-4e35-a38c-711bd1c28948:172.27.80.23:9858, ff544de8-96ea-4097-8cdc-460ac1c60db7:172.27.23.161:9858
> 2018-09-09 10:49:40,209 INFO org.apache.ratis.server.impl.RaftServerProxy: bfe9c5f2-da9b-4a8f-9013-7540cbbed1c9: reinitializeAsync ReinitializeRequest(client-DFE3ACF394F9->bfe9c5f2-da9b-4a8f-9013-7540cbbed1c9) in group-7347726F7570, cid=3, seq=0 RW, null, group-2041ABBEE452:[bfe9c5f2-da9b-4a8f-9013-7540cbbed1c9:172.27.12.96:9858, faa888b7-92bb-4e35-a38c-711bd1c28948:172.27.80.23:9858, ff544de8-96ea-4097-8cdc-460ac1c60db7:172.27.23.161:9858]
> {code}
> But around the same time, the third server is not ready
> {code:java}
> 2018-09-09 10:49:41,414 WARN org.apache.ratis.grpc.server.RaftServerProtocolService: ff544de8-96ea-4097-8cdc-460ac1c60db7: Failed requestVote bfe9c5f2-da9b-4a8f-9013-7540cbbed1c9->ff544de8-96ea-4097-8cdc-460ac1c60db7#0: org.apache.ratis.protocol.ServerNotReadyException: Server ff544de8-96ea-4097-8cdc-460ac1c60db7 is not [RUNNING]: current state is STARTING
> {code}
> Though the reinitialization request never got processed on this server, the exception is ignored in RaftClientImpl. This needs to be addressed
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)