[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
]
runzhiwang updated RATIS-840:
-
Description:
*What's the problem ?*
When run hadoop-ozone for 4 days, datanode memory leak. When dump heap, I
found there are 460710 instances of GrpcLogAppender. But there are only 6
instances of SenderList, and each SenderList contains 1-2 instance of
GrpcLogAppender. And there are a lot of logs related to
[LeaderState::restartSender|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LeaderState.java#L428].
{code:java}INFO impl.RaftServerImpl:
1665f5ea-ab17-4a0e-af6d-6958efd322fa@group-F64B465F37B5-LeaderState: Restarting
GrpcLogAppender for
1665f5ea-ab17-4a0e-af6d-6958efd322fa@group-F64B465F37B5-\u003e229cbcc1-a3b2-4383-9c0d-c0f4c28c3d4a\n","stream":"stderr","time":"2020-04-06T03:59:53.37892512Z"}{code}
So there are a lot of GrpcLogAppender did not stop the Daemon Thread when
removed from senders.
!image-2020-04-06-14-27-28-485.png!
!image-2020-04-06-14-27-39-582.png!
*Why
[LeaderState::restartSender|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LeaderState.java#L428]
so many times ?*
1. As the image shows, when remove group, SegmentedRaftLog will close, then
GrpcLogAppender throw exception when find the SegmentedRaftLog was closed. Then
GrpcLogAppender will be
[restarted|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LogAppender.java#L94],
and the new GrpcLogAppender throw exception again when find the
SegmentedRaftLog was closed, then GrpcLogAppender will be restarted again ... .
It results in an infinite restart of GrpcLogAppender.
2. Actually, when remove group, GrpcLogAppender will be stoped:
RaftServerImpl::shutdown ->
[RoleInfo::shutdownLeaderState|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/RaftServerImpl.java#L266]
-> LeaderState::stop -> LogAppender::stopAppender, then SegmentedRaftLog will
be closed: RaftServerImpl::shutdown ->
[ServerState:close|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/RaftServerImpl.java#L271]
... . Though RoleInfo::shutdownLeaderState called before ServerState:close,
but the GrpcLogAppender was stopped asynchronously. So infinite restart of
GrpcLogAppender happens, when GrpcLogAppender stop after SegmentedRaftLog close.
!screenshot-1.png!
*Why GrpcLogAppender did not stop the Daemon Thread when removed from senders ?*
h1. {color:#DE350B}Still working. The previous patch has some problem, and I
will submit it again.{color}
*Can the new GrpcLogAppender work normally ?*
1. Even though without the above problem, the new created GrpcLogAppender still
can not work normally.
2. When creat a new GrpcLogAppender, a new FollowerInfo will also be created:
LeaderState::addAndStartSenders ->
LeaderState::addSenders->RaftServerImpl::newLogAppender -> [new
FollowerInfo|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/RaftServerImpl.java#L129]
3. When the new created GrpcLogAppender append entry to follower, then the
follower response SUCCESS.
4. Then LeaderState::updateCommit -> [LeaderState::getMajorityMin |
https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LeaderState.java#L599]
->
[voterLists.get(0) |
https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LeaderState.java#L607].
{color:#DE350B}Error happens because voterLists.get(0) return the FollowerInfo
of the old GrpcLogAppender, not the FollowerInfo of the new GrpcLogAppender.
{color}
5. Because the majority commit got from the FollowerInfo of the old
GrpcLogAppender never changes. So even though follower has append entry
successfully, the leader can not update commit. So the new created
GrpcLogAppender can never work normally.
6. The reason of unit test of runTestRestartLogAppender can pass is that it did
not stop the old GrpcLogAppender, and the old GrpcLogAppender append entry to
follower, not the new GrpcLogAppender. If stop the old GrpcLogAppender,
runTestRestartLogAppender will fail.
was:
*What's the problem ?*
When run hadoop-ozone for 4 days, datanode memory leak. When dump heap, I
found there are 460710 instances of GrpcLogAppender. But there are only 6
instances of SenderList, and each SenderList contains 1-2 instance of
GrpcLogAppender. And there are a lot of logs related to
[LeaderState::restartSender|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LeaderState.java#L428].
{code:java}INFO
[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
]
runzhiwang updated RATIS-840:
-
Description:
*What's the problem ?*
When run hadoop-ozone for 4 days, datanode memory leak. When dump heap, I
found there are 460710 instances of GrpcLogAppender. But there are only 6
instances of SenderList, and each SenderList contains 1-2 instance of
GrpcLogAppender. And there are a lot of logs related to
[LeaderState::restartSender|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LeaderState.java#L428].
{code:java}INFO impl.RaftServerImpl:
1665f5ea-ab17-4a0e-af6d-6958efd322fa@group-F64B465F37B5-LeaderState: Restarting
GrpcLogAppender for
1665f5ea-ab17-4a0e-af6d-6958efd322fa@group-F64B465F37B5-\u003e229cbcc1-a3b2-4383-9c0d-c0f4c28c3d4a\n","stream":"stderr","time":"2020-04-06T03:59:53.37892512Z"}{code}
So there are a lot of GrpcLogAppender did not stop the Daemon Thread when
removed from senders.
!image-2020-04-06-14-27-28-485.png!
!image-2020-04-06-14-27-39-582.png!
*Why
[LeaderState::restartSender|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LeaderState.java#L428]
so many times ?*
1. As the image shows, when remove group, SegmentedRaftLog will close, then
GrpcLogAppender throw exception when find the SegmentedRaftLog was closed. Then
GrpcLogAppender will be
[restarted|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LogAppender.java#L94],
and the new GrpcLogAppender throw exception again when find the
SegmentedRaftLog was closed, then GrpcLogAppender will be restarted again ... .
It results in an infinite restart of GrpcLogAppender.
2. Actually, when remove group, GrpcLogAppender will be stoped:
RaftServerImpl::shutdown ->
[RoleInfo::shutdownLeaderState|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/RaftServerImpl.java#L266]
-> LeaderState::stop -> LogAppender::stopAppender, then SegmentedRaftLog will
be closed: RaftServerImpl::shutdown ->
[ServerState:close|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/RaftServerImpl.java#L271]
... . Though RoleInfo::shutdownLeaderState called before ServerState:close,
but the GrpcLogAppender was stopped asynchronously. So infinite restart of
GrpcLogAppender happens, when GrpcLogAppender stop after SegmentedRaftLog close.
!screenshot-1.png!
h1. *Why GrpcLogAppender did not stop the Daemon Thread when removed from
senders ?*
h1. {color:#DE350B}Still working. The previous patch has some problem, and I
will submit it again.{color}
*Can the new GrpcLogAppender work normally ?*
1. Even though without the above problem, the new created GrpcLogAppender still
can not work normally.
2. When creat a new GrpcLogAppender, a new FollowerInfo will also be created:
LeaderState::addAndStartSenders ->
LeaderState::addSenders->RaftServerImpl::newLogAppender -> [new
FollowerInfo|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/RaftServerImpl.java#L129]
3. When the new created GrpcLogAppender append entry to follower, then the
follower response SUCCESS.
4. Then LeaderState::updateCommit -> [LeaderState::getMajorityMin |
https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LeaderState.java#L599]
->
[voterLists.get(0) |
https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LeaderState.java#L607].
{color:#DE350B}Error happens because voterLists.get(0) return the FollowerInfo
of the old GrpcLogAppender, not the FollowerInfo of the new GrpcLogAppender.
{color}
5. Because the majority commit got from the FollowerInfo of the old
GrpcLogAppender never changes. So even though follower has append entry
successfully, the leader can not update commit. So the new created
GrpcLogAppender can never work normally.
6. The reason of unit test of runTestRestartLogAppender can pass is that it did
not stop the old GrpcLogAppender, and the old GrpcLogAppender append entry to
follower, not the new GrpcLogAppender. If stop the old GrpcLogAppender,
runTestRestartLogAppender will fail.
was:
*What's the problem ?*
When run hadoop-ozone for 4 days, datanode memory leak. When dump heap, I
found there are 460710 instances of GrpcLogAppender. But there are only 6
instances of SenderList, and each SenderList contains 1-2 instance of
GrpcLogAppender. And there are a lot of logs related to
[LeaderState::restartSender|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LeaderState.java#L428].
{code:java}INFO
[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
> --
>
> Key: RATIS-840
> URL: https://issues.apache.org/jira/browse/RATIS-840
> Project: Ratis
> Issue Type: Bug
> Components: server
>Reporter: runzhiwang
>Assignee: runzhiwang
>Priority: Critical
> Attachments: image-2020-04-06-14-27-28-485.png,
> image-2020-04-06-14-27-39-582.png, screenshot-1.png
>
>
> *What's the problem ?*
> When run hadoop-ozone for 4 days, datanode memory leak. When dump heap, I
> found there are 460710 instances of GrpcLogAppender. But there are only 6
> instances of SenderList, and each SenderList contains 1-2 instance of
> GrpcLogAppender. And there are a lot of logs related to
> [LeaderState::restartSender|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LeaderState.java#L428].
> {code:java}INFO impl.RaftServerImpl:
> 1665f5ea-ab17-4a0e-af6d-6958efd322fa@group-F64B465F37B5-LeaderState:
> Restarting GrpcLogAppender for
> 1665f5ea-ab17-4a0e-af6d-6958efd322fa@group-F64B465F37B5-\u003e229cbcc1-a3b2-4383-9c0d-c0f4c28c3d4a\n","stream":"stderr","time":"2020-04-06T03:59:53.37892512Z"}{code}
>
> So there are a lot of GrpcLogAppender did not stop the Daemon Thread when
> removed from senders.
> !image-2020-04-06-14-27-28-485.png!
> !image-2020-04-06-14-27-39-582.png!
>
> *Why
> [LeaderState::restartSender|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LeaderState.java#L428]
> so many times ?*
> 1. As the image shows, when remove group, SegmentedRaftLog will close, then
> GrpcLogAppender throw exception when find the SegmentedRaftLog was closed.
> Then GrpcLogAppender will be
> [restarted|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LogAppender.java#L94],
> and the new GrpcLogAppender throw exception again when find the
> SegmentedRaftLog was closed, then GrpcLogAppender will be restarted again ...
> . It results in an infinite restart of GrpcLogAppender.
> 2. Actually, when remove group, GrpcLogAppender will be stoped:
> RaftServerImpl::shutdown ->
> [RoleInfo::shutdownLeaderState|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/RaftServerImpl.java#L266]
> -> LeaderState::stop -> LogAppender::stopAppender, then SegmentedRaftLog
> will be closed: RaftServerImpl::shutdown ->
> [ServerState:close|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/RaftServerImpl.java#L271]
> ... . Though RoleInfo::shutdownLeaderState called before ServerState:close,
> but the GrpcLogAppender was stopped asynchronously. So infinite restart of
> GrpcLogAppender happens, when GrpcLogAppender stop after SegmentedRaftLog
> close.
> !screenshot-1.png!
> *Why GrpcLogAppender did not stop the Daemon Thread when removed from senders
> ?*
> {color:#DE350B}Still working. The previous patch has some problem, and I will
> submit it again.{color}
> *Can the new GrpcLogAppender work normally ?*
> 1. Even though without the above problem, the new created GrpcLogAppender
> still can not work normally.
> 2. When creat a new GrpcLogAppender, a new FollowerInfo will also be created:
> LeaderState::addAndStartSenders ->
> LeaderState::addSenders->RaftServerImpl::newLogAppender -> [new
> FollowerInfo|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/RaftServerImpl.java#L129]
> 3. When the new created GrpcLogAppender append entry to follower, then the
> follower response SUCCESS.
> 4. Then LeaderState::updateCommit -> [LeaderState::getMajorityMin |
> https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LeaderState.java#L599]
> ->
> [voterLists.get(0) |
> https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LeaderState.java#L607].
> {color:#DE350B}Error happens because voterLists.get(0) return the
> FollowerInfo of the old GrpcLogAppender, not the FollowerInfo of the new
> GrpcLogAppender. {color}
> 5. Because the majority commit got from the FollowerInfo of the old
> GrpcLogAppender never changes. So even though follower has append entry
> successfully, the leader can not update commit. So the new created
> GrpcLogAppender can never work normally.
> 6. The reason of unit test of runTestRestartLogAppender can pass is that it
> did not stop the old GrpcLogAppender, and the old GrpcLogAppender append
[jira] [Updated] (RATIS-854) Update download links
[ https://issues.apache.org/jira/browse/RATIS-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated RATIS-854: Description: The download links for signatures/checksums/KEYS should be updated from dist.apache.org to https://downloads.apache.org/incubator/ratis/ (was: The download lists for signatures/checksums/KEYS should be updated from dist.apache.org to https://downloads.apache.org/incubator/ratis/) > Update download links > - > > Key: RATIS-854 > URL: https://issues.apache.org/jira/browse/RATIS-854 > Project: Ratis > Issue Type: Improvement > Components: website >Reporter: Arpit Agarwal >Priority: Major > Labels: newbie > > The download links for signatures/checksums/KEYS should be updated from > dist.apache.org to https://downloads.apache.org/incubator/ratis/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Moved] (RATIS-854) Update download links
[ https://issues.apache.org/jira/browse/RATIS-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal moved HDDS-3410 to RATIS-854: --- Component/s: (was: website) website Key: RATIS-854 (was: HDDS-3410) Workflow: no-reopen-closed, patch-avail (was: patch-available, re-open possible) Project: Ratis (was: Hadoop Distributed Data Store) > Update download links > - > > Key: RATIS-854 > URL: https://issues.apache.org/jira/browse/RATIS-854 > Project: Ratis > Issue Type: Improvement > Components: website >Reporter: Arpit Agarwal >Priority: Major > Labels: newbie > > The download lists for signatures/checksums/KEYS should be updated from > dist.apache.org to https://downloads.apache.org/hadoop/ozone/. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RATIS-854) Update download links
[ https://issues.apache.org/jira/browse/RATIS-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated RATIS-854: Description: The download lists for signatures/checksums/KEYS should be updated from dist.apache.org to https://downloads.apache.org/incubator/ratis/ (was: The download lists for signatures/checksums/KEYS should be updated from dist.apache.org to https://downloads.apache.org/hadoop/ozone/.) > Update download links > - > > Key: RATIS-854 > URL: https://issues.apache.org/jira/browse/RATIS-854 > Project: Ratis > Issue Type: Improvement > Components: website >Reporter: Arpit Agarwal >Priority: Major > Labels: newbie > > The download lists for signatures/checksums/KEYS should be updated from > dist.apache.org to https://downloads.apache.org/incubator/ratis/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RATIS-840) Memory leak of LogAppender
[
https://issues.apache.org/jira/browse/RATIS-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17085273#comment-17085273
]
Tsz-wo Sze commented on RATIS-840:
--
> ... Error happens because voterLists.get(0) return the FollowerInfo of the
> old GrpcLogAppender, not the FollowerInfo of the new GrpcLogAppender. ...
Good catch! It seems better to change voterLists to use RaftPeerId, i.e.
{code}
List> voterLists;
{code}
and then get the FollowerInfo from SenderList.
Look forward to see you patch. Thanks a lot.
> Memory leak of LogAppender
> --
>
> Key: RATIS-840
> URL: https://issues.apache.org/jira/browse/RATIS-840
> Project: Ratis
> Issue Type: Bug
> Components: server
>Reporter: runzhiwang
>Assignee: runzhiwang
>Priority: Major
> Attachments: image-2020-04-06-14-27-28-485.png,
> image-2020-04-06-14-27-39-582.png, screenshot-1.png
>
>
> *What's the problem ?*
> When run hadoop-ozone for 4 days, datanode memory leak. When dump heap, I
> found there are 460710 instances of GrpcLogAppender. But there are only 6
> instances of SenderList, and each SenderList contains 1-2 instance of
> GrpcLogAppender. And there are a lot of logs related to
> [LeaderState::restartSender|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LeaderState.java#L428].
> {code:java}INFO impl.RaftServerImpl:
> 1665f5ea-ab17-4a0e-af6d-6958efd322fa@group-F64B465F37B5-LeaderState:
> Restarting GrpcLogAppender for
> 1665f5ea-ab17-4a0e-af6d-6958efd322fa@group-F64B465F37B5-\u003e229cbcc1-a3b2-4383-9c0d-c0f4c28c3d4a\n","stream":"stderr","time":"2020-04-06T03:59:53.37892512Z"}{code}
>
> So there are a lot of GrpcLogAppender did not stop the Daemon Thread when
> removed from senders.
> !image-2020-04-06-14-27-28-485.png!
> !image-2020-04-06-14-27-39-582.png!
>
> *Why
> [LeaderState::restartSender|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LeaderState.java#L428]
> so many times ?*
> 1. As the image shows, when remove group, SegmentedRaftLog will close, then
> GrpcLogAppender throw exception when find the SegmentedRaftLog was closed.
> Then GrpcLogAppender will be
> [restarted|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LogAppender.java#L94],
> and the new GrpcLogAppender throw exception again when find the
> SegmentedRaftLog was closed, then GrpcLogAppender will be restarted again ...
> . It results in an infinite restart of GrpcLogAppender.
> 2. Actually, when remove group, GrpcLogAppender will be stoped:
> RaftServerImpl::shutdown ->
> [RoleInfo::shutdownLeaderState|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/RaftServerImpl.java#L266]
> -> LeaderState::stop -> LogAppender::stopAppender, then SegmentedRaftLog
> will be closed: RaftServerImpl::shutdown ->
> [ServerState:close|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/RaftServerImpl.java#L271]
> ... . Though RoleInfo::shutdownLeaderState called before ServerState:close,
> but the GrpcLogAppender was stopped asynchronously. So infinite restart of
> GrpcLogAppender happens, when GrpcLogAppender stop after SegmentedRaftLog
> close.
> !screenshot-1.png!
> *Why GrpcLogAppender did not stop the Daemon Thread when removed from senders
> ?*
> {color:#DE350B}Still working. The previous patch has some problem, and I will
> submit it again.{color}
> *Can the new GrpcLogAppender work normally ?*
> 1. Even though without the above problem, the new created GrpcLogAppender
> still can not work normally.
> 2. When creat a new GrpcLogAppender, a new FollowerInfo will also be created:
> LeaderState::addAndStartSenders ->
> LeaderState::addSenders->RaftServerImpl::newLogAppender -> [new
> FollowerInfo|https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/RaftServerImpl.java#L129]
> 3. When the new created GrpcLogAppender append entry to follower, then the
> follower response SUCCESS.
> 4. Then LeaderState::updateCommit -> [LeaderState::getMajorityMin |
> https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LeaderState.java#L599]
> ->
> [voterLists.get(0) |
> https://github.com/apache/incubator-ratis/blob/master/ratis-server/src/main/java/org/apache/ratis/server/impl/LeaderState.java#L607].
> {color:#DE350B}Error happens because voterLists.get(0) return the
> FollowerInfo of the old GrpcLogAppender, not the FollowerInfo of the new
> GrpcLogAppender. {color}
> 5. Because the majority commit got from the FollowerInfo of the old
>
[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=17085037#comment-17085037 ] Lokesh Jain commented on RATIS-853: --- [~shashikant] The patch is rebased upon RATIS-835. > Unordered Client request should not sleep when NotLeaderException provides > leader information > - > > Key: RATIS-853 > URL: https://issues.apache.org/jira/browse/RATIS-853 > Project: Ratis > Issue Type: Bug > Components: client >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Major > Attachments: RATIS-853.001.patch > > > When NotLeaderException provides leader information, the client request > should be retried immediately on the suggested leader. Currently Unordered > requests in raft client use the default policy to determine sleep time and > thus may sleep even if NotLeaderException provides leader information. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[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=17084878#comment-17084878
]
Hadoop QA commented on RATIS-853:
-
| (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 7s{color}
| {color:red} RATIS-853 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-853 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/13000135/RATIS-853.001.patch |
| Console output |
https://builds.apache.org/job/PreCommit-RATIS-Build/1289/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> Unordered Client request should not sleep when NotLeaderException provides
> leader information
> -
>
> Key: RATIS-853
> URL: https://issues.apache.org/jira/browse/RATIS-853
> Project: Ratis
> Issue Type: Bug
> Components: client
>Reporter: Lokesh Jain
>Assignee: Lokesh Jain
>Priority: Major
> Attachments: RATIS-853.001.patch
>
>
> When NotLeaderException provides leader information, the client request
> should be retried immediately on the suggested leader. Currently Unordered
> requests in raft client use the default policy to determine sleep time and
> thus may sleep even if NotLeaderException provides leader information.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (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:all-tabpanel ] Lokesh Jain updated RATIS-853: -- Attachment: RATIS-853.001.patch > Unordered Client request should not sleep when NotLeaderException provides > leader information > - > > Key: RATIS-853 > URL: https://issues.apache.org/jira/browse/RATIS-853 > Project: Ratis > Issue Type: Bug > Components: client >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Major > Attachments: RATIS-853.001.patch > > > When NotLeaderException provides leader information, the client request > should be retried immediately on the suggested leader. Currently Unordered > requests in raft client use the default policy to determine sleep time and > thus may sleep even if NotLeaderException provides leader information. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (RATIS-853) Unordered Client request should not sleep when NotLeaderException provides leader information
Lokesh Jain created RATIS-853: - Summary: Unordered Client request should not sleep when NotLeaderException provides leader information Key: RATIS-853 URL: https://issues.apache.org/jira/browse/RATIS-853 Project: Ratis Issue Type: Bug Components: client Reporter: Lokesh Jain Assignee: Lokesh Jain When NotLeaderException provides leader information, the client request should be retried immediately on the suggested leader. Currently Unordered requests in raft client use the default policy to determine sleep time and thus may sleep even if NotLeaderException provides leader information. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[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 committed this. > Raft Client should not change leader on ResourceUnavailableException > > > Key: RATIS-851 > URL: https://issues.apache.org/jira/browse/RATIS-851 > Project: Ratis > Issue Type: Bug > Components: client >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Major > Attachments: RATIS-851.001.patch > > > Currently raft client changes the leader on receiving > ResourceUnavailableException. It should not change the leader as the > exception only signifies load on the leader. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[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 look good to me. I am +1 on this. > Raft Client should not change leader on ResourceUnavailableException > > > Key: RATIS-851 > URL: https://issues.apache.org/jira/browse/RATIS-851 > Project: Ratis > Issue Type: Bug > Components: client >Reporter: Lokesh Jain >Assignee: Lokesh Jain >Priority: Major > Attachments: RATIS-851.001.patch > > > Currently raft client changes the leader on receiving > ResourceUnavailableException. It should not change the leader as the > exception only signifies load on the leader. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RATIS-844) RaftClient should connect to the new leader when the old leader is partitioned from the cluster
[ https://issues.apache.org/jira/browse/RATIS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084687#comment-17084687 ] Burcu Ozkan commented on RATIS-844: --- Thanks for checking the bug. Yes, I'll provide a patch. > RaftClient should connect to the new leader when the old leader is > partitioned from the cluster > --- > > Key: RATIS-844 > URL: https://issues.apache.org/jira/browse/RATIS-844 > Project: Ratis > Issue Type: Bug > Components: client >Affects Versions: 0.6.0 >Reporter: Burcu Ozkan >Priority: Major > Attachments: RATIS-844.001.patch > > > While running a Netty cluster, RaftClient is blocked after it submits a > request to the leader which is partitioned from the cluster. > The attached test reproduces the problem. In the test, after the client > connects to the leader, the leader is disconnected and another node is > elected as the new leader. However, the client waits indefinitely for a reply > from the previous one. > The test passes for Grpc and HadoopRpc, but fails with TestTimedOutException > for Netty. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RATIS-844) RaftClient should connect to the new leader when the old leader is partitioned from the cluster
[ https://issues.apache.org/jira/browse/RATIS-844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084652#comment-17084652 ] Lokesh Jain commented on RATIS-844: --- [~burcukozkan] Thanks for raising the bug and providing the unit test! UT works for Grpc because we added timeout handling for requests sent via grpc in RATIS-214 and RATIS-215. Would you like to provide a patch for adding timeouts to requests sent via netty? > RaftClient should connect to the new leader when the old leader is > partitioned from the cluster > --- > > Key: RATIS-844 > URL: https://issues.apache.org/jira/browse/RATIS-844 > Project: Ratis > Issue Type: Bug > Components: client >Affects Versions: 0.6.0 >Reporter: Burcu Ozkan >Priority: Major > Attachments: RATIS-844.001.patch > > > While running a Netty cluster, RaftClient is blocked after it submits a > request to the leader which is partitioned from the cluster. > The attached test reproduces the problem. In the test, after the client > connects to the leader, the leader is disconnected and another node is > elected as the new leader. However, the client waits indefinitely for a reply > from the previous one. > The test passes for Grpc and HadoopRpc, but fails with TestTimedOutException > for Netty. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RATIS-847) Upgrade netty, grpc, protobuf and netty.tcnative version in ratis-thirdparty
[ https://issues.apache.org/jira/browse/RATIS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-847: -- Fix Version/s: (was: 0.4.0) > Upgrade netty, grpc, protobuf and netty.tcnative version in ratis-thirdparty > > > Key: RATIS-847 > URL: https://issues.apache.org/jira/browse/RATIS-847 > Project: Ratis > Issue Type: Bug > Components: thirdparty >Reporter: Lokesh Jain >Assignee: Mukul Kumar Singh >Priority: Major > Attachments: RATIS-847.001.patch, RATIS-847.002.patch, > RATIS-847.003.patch > > > The Jira aims to upgrade netty(4.1.48.Final), grpc(1.28.1), protobuf(3.11.0) > and netty.tcnative(2.0.28.Final) version in ratis-thirdparty. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (RATIS-847) Upgrade netty, grpc, protobuf and netty.tcnative version in ratis-thirdparty
[ https://issues.apache.org/jira/browse/RATIS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain resolved RATIS-847. --- Fix Version/s: 0.4.0 Target Version/s: (was: 0.6.0) Resolution: Fixed > Upgrade netty, grpc, protobuf and netty.tcnative version in ratis-thirdparty > > > Key: RATIS-847 > URL: https://issues.apache.org/jira/browse/RATIS-847 > Project: Ratis > Issue Type: Bug > Components: thirdparty >Reporter: Lokesh Jain >Assignee: Mukul Kumar Singh >Priority: Major > Fix For: 0.4.0 > > Attachments: RATIS-847.001.patch, RATIS-847.002.patch, > RATIS-847.003.patch > > > The Jira aims to upgrade netty(4.1.48.Final), grpc(1.28.1), protobuf(3.11.0) > and netty.tcnative(2.0.28.Final) version in ratis-thirdparty. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RATIS-847) Upgrade netty, grpc, protobuf and netty.tcnative version in ratis-thirdparty
[ https://issues.apache.org/jira/browse/RATIS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084642#comment-17084642 ] Lokesh Jain commented on RATIS-847: --- [~msingh] Thanks for the contribution! I have committed the patch to master branch. > Upgrade netty, grpc, protobuf and netty.tcnative version in ratis-thirdparty > > > Key: RATIS-847 > URL: https://issues.apache.org/jira/browse/RATIS-847 > Project: Ratis > Issue Type: Bug > Components: thirdparty >Reporter: Lokesh Jain >Assignee: Mukul Kumar Singh >Priority: Major > Attachments: RATIS-847.001.patch, RATIS-847.002.patch, > RATIS-847.003.patch > > > The Jira aims to upgrade netty(4.1.48.Final), grpc(1.28.1), protobuf(3.11.0) > and netty.tcnative(2.0.28.Final) version in ratis-thirdparty. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RATIS-847) Upgrade netty, grpc, protobuf and netty.tcnative version in ratis-thirdparty
[ https://issues.apache.org/jira/browse/RATIS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-847: -- Description: The Jira aims to upgrade netty(4.1.48.Final), grpc(1.28.1), protobuf(3.11.0) and netty.tcnative(2.0.28.Final) version in ratis-thirdparty. (was: We should upgrade netty version to 4.1.48.Final, ) > Upgrade netty, grpc, protobuf and netty.tcnative version in ratis-thirdparty > > > Key: RATIS-847 > URL: https://issues.apache.org/jira/browse/RATIS-847 > Project: Ratis > Issue Type: Bug > Components: thirdparty >Reporter: Lokesh Jain >Assignee: Mukul Kumar Singh >Priority: Major > Attachments: RATIS-847.001.patch, RATIS-847.002.patch, > RATIS-847.003.patch > > > The Jira aims to upgrade netty(4.1.48.Final), grpc(1.28.1), protobuf(3.11.0) > and netty.tcnative(2.0.28.Final) version in ratis-thirdparty. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RATIS-847) Upgrade netty, grpc, protobuf and netty.tcnative version in ratis-thirdparty
[ https://issues.apache.org/jira/browse/RATIS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-847: -- Description: We should upgrade netty version to 4.1.48.Final, (was: We should upgrade netty version to 4.1.48.Final. We are currently on 4.1.46.Final) > Upgrade netty, grpc, protobuf and netty.tcnative version in ratis-thirdparty > > > Key: RATIS-847 > URL: https://issues.apache.org/jira/browse/RATIS-847 > Project: Ratis > Issue Type: Bug > Components: thirdparty >Reporter: Lokesh Jain >Assignee: Mukul Kumar Singh >Priority: Major > Attachments: RATIS-847.001.patch, RATIS-847.002.patch, > RATIS-847.003.patch > > > We should upgrade netty version to 4.1.48.Final, -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RATIS-847) Upgrade netty, grpc, protobuf and netty.tcnative version in ratis-thirdparty
[ https://issues.apache.org/jira/browse/RATIS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084637#comment-17084637 ] Lokesh Jain commented on RATIS-847: --- [~msingh] Thanks for updating the patch! The changes look good to me. +1. > Upgrade netty, grpc, protobuf and netty.tcnative version in ratis-thirdparty > > > Key: RATIS-847 > URL: https://issues.apache.org/jira/browse/RATIS-847 > Project: Ratis > Issue Type: Bug > Components: thirdparty >Reporter: Lokesh Jain >Assignee: Mukul Kumar Singh >Priority: Major > Attachments: RATIS-847.001.patch, RATIS-847.002.patch, > RATIS-847.003.patch > > > We should upgrade netty version to 4.1.48.Final. We are currently on > 4.1.46.Final -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RATIS-847) Upgrade netty, grpc, protobuf and netty.tcnative version in ratis-thirdparty
[ https://issues.apache.org/jira/browse/RATIS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated RATIS-847: -- Summary: Upgrade netty, grpc, protobuf and netty.tcnative version in ratis-thirdparty (was: Upgrade netty to 4.1.48.Final) > Upgrade netty, grpc, protobuf and netty.tcnative version in ratis-thirdparty > > > Key: RATIS-847 > URL: https://issues.apache.org/jira/browse/RATIS-847 > Project: Ratis > Issue Type: Bug > Components: thirdparty >Reporter: Lokesh Jain >Priority: Major > Attachments: RATIS-847.001.patch, RATIS-847.002.patch, > RATIS-847.003.patch > > > We should upgrade netty version to 4.1.48.Final. We are currently on > 4.1.46.Final -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (RATIS-847) Upgrade netty, grpc, protobuf and netty.tcnative version in ratis-thirdparty
[ https://issues.apache.org/jira/browse/RATIS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain reassigned RATIS-847: - Assignee: Mukul Kumar Singh > Upgrade netty, grpc, protobuf and netty.tcnative version in ratis-thirdparty > > > Key: RATIS-847 > URL: https://issues.apache.org/jira/browse/RATIS-847 > Project: Ratis > Issue Type: Bug > Components: thirdparty >Reporter: Lokesh Jain >Assignee: Mukul Kumar Singh >Priority: Major > Attachments: RATIS-847.001.patch, RATIS-847.002.patch, > RATIS-847.003.patch > > > We should upgrade netty version to 4.1.48.Final. We are currently on > 4.1.46.Final -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (RATIS-852) GrpcSslTest fails with CertificateExpiredException
[
https://issues.apache.org/jira/browse/RATIS-852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084606#comment-17084606
]
Lokesh Jain commented on RATIS-852:
---
I have committed this to ratis-thirrdparty repo.
> GrpcSslTest fails with CertificateExpiredException
> --
>
> Key: RATIS-852
> URL: https://issues.apache.org/jira/browse/RATIS-852
> Project: Ratis
> Issue Type: Bug
> Components: thirdparty
>Reporter: Mukul Kumar Singh
>Assignee: Mukul Kumar Singh
>Priority: Major
> Attachments: RATIS-852.001.patch
>
>
> GrpcSslTest fails with CertificateExpiredException
> {code}
> [INFO] Running org.apache.ratis.thirdparty.demo.GrpcSslTest
> 2020-04-16 11:40:30,624 [Thread-0] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/server.pem
> 2020-04-16 11:40:30,624 [main] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/client.pem
> 2020-04-16 11:40:30,627 [Thread-0] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/server.crt
> 2020-04-16 11:40:30,629 [main] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/ca.crt
> 2020-04-16 11:40:30,629 [Thread-0] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/client.crt
> 2020-04-16 11:40:30,630 [main] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/client.crt
> 2020-04-16 11:40:31,224 [Thread-0] INFO demo.GrpcServer
> (GrpcSslServer.java:start(69)) - GrpcSslServer started, listening on 50005
> 2020-04-16 11:40:31,454 [main] WARN demo.GrpcSslClient
> (GrpcSslClient.java:greet(86)) - RPC failed: {0}
> org.apache.ratis.thirdparty.io.grpc.StatusRuntimeException: UNAVAILABLE: io
> exception
> Channel Pipeline: [SslHandler#0, ProtocolNegotiators$ClientTlsHandler#0,
> WriteBufferingAndExceptionHandler#0, DefaultChannelPipeline$TailContext#0]
> at
> org.apache.ratis.thirdparty.io.grpc.stub.ClientCalls.toStatusRuntimeException(ClientCalls.java:235)
> at
> org.apache.ratis.thirdparty.io.grpc.stub.ClientCalls.getUnchecked(ClientCalls.java:216)
> at
> org.apache.ratis.thirdparty.io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:141)
> at
> org.apache.ratis.thirdparty.demo.GreeterGrpc$GreeterBlockingStub.hello(GreeterGrpc.java:156)
> at
> org.apache.ratis.thirdparty.demo.GrpcSslClient.greet(GrpcSslClient.java:82)
> at
> org.apache.ratis.thirdparty.demo.GrpcSslTest.testSslClientServer(GrpcSslTest.java:73)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
>
[jira] [Commented] (RATIS-852) GrpcSslTest fails with CertificateExpiredException
[
https://issues.apache.org/jira/browse/RATIS-852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084603#comment-17084603
]
Lokesh Jain commented on RATIS-852:
---
[~msingh] Thanks for working on this! The changes look good to me. +1.
> GrpcSslTest fails with CertificateExpiredException
> --
>
> Key: RATIS-852
> URL: https://issues.apache.org/jira/browse/RATIS-852
> Project: Ratis
> Issue Type: Bug
> Components: thirdparty
>Reporter: Mukul Kumar Singh
>Assignee: Mukul Kumar Singh
>Priority: Major
> Attachments: RATIS-852.001.patch
>
>
> GrpcSslTest fails with CertificateExpiredException
> {code}
> [INFO] Running org.apache.ratis.thirdparty.demo.GrpcSslTest
> 2020-04-16 11:40:30,624 [Thread-0] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/server.pem
> 2020-04-16 11:40:30,624 [main] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/client.pem
> 2020-04-16 11:40:30,627 [Thread-0] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/server.crt
> 2020-04-16 11:40:30,629 [main] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/ca.crt
> 2020-04-16 11:40:30,629 [Thread-0] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/client.crt
> 2020-04-16 11:40:30,630 [main] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/client.crt
> 2020-04-16 11:40:31,224 [Thread-0] INFO demo.GrpcServer
> (GrpcSslServer.java:start(69)) - GrpcSslServer started, listening on 50005
> 2020-04-16 11:40:31,454 [main] WARN demo.GrpcSslClient
> (GrpcSslClient.java:greet(86)) - RPC failed: {0}
> org.apache.ratis.thirdparty.io.grpc.StatusRuntimeException: UNAVAILABLE: io
> exception
> Channel Pipeline: [SslHandler#0, ProtocolNegotiators$ClientTlsHandler#0,
> WriteBufferingAndExceptionHandler#0, DefaultChannelPipeline$TailContext#0]
> at
> org.apache.ratis.thirdparty.io.grpc.stub.ClientCalls.toStatusRuntimeException(ClientCalls.java:235)
> at
> org.apache.ratis.thirdparty.io.grpc.stub.ClientCalls.getUnchecked(ClientCalls.java:216)
> at
> org.apache.ratis.thirdparty.io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:141)
> at
> org.apache.ratis.thirdparty.demo.GreeterGrpc$GreeterBlockingStub.hello(GreeterGrpc.java:156)
> at
> org.apache.ratis.thirdparty.demo.GrpcSslClient.greet(GrpcSslClient.java:82)
> at
> org.apache.ratis.thirdparty.demo.GrpcSslTest.testSslClientServer(GrpcSslTest.java:73)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at
>
[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=17084584#comment-17084584
]
Hadoop QA commented on RATIS-851:
-
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
59s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:blue}0{color} | {color:blue} findbugs {color} | {color:blue} 0m
0s{color} | {color:blue} Findbugs executables are not available. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m
0s{color} | {color:red} The patch doesn't appear to include any new or modified
tests. Please justify why no new tests are needed for this patch. Also please
list what manual steps were performed to verify this patch. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
7s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
56s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
20s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
47s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
2s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
53s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
53s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
10s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
39s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 30m 51s{color}
| {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
19s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 42m 16s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | ratis.logservice.TestLogServiceWithNetty |
| | ratis.logservice.server.TestMetaServer |
| | ratis.server.simulation.TestRaftExceptionWithSimulation |
| | ratis.netty.TestRaftStateMachineExceptionWithNetty |
| | ratis.server.simulation.TestRaftStateMachineExceptionWithSimulatedRpc |
| | ratis.netty.TestRaftSnapshotWithNetty |
| | ratis.grpc.TestRaftSnapshotWithGrpc |
| | ratis.server.simulation.TestRaftSnapshotWithSimulatedRpc |
| | ratis.server.simulation.TestRaftWithSimulatedRpc |
| | ratis.examples.filestore.TestFileStoreWithGrpc |
| | ratis.examples.filestore.TestFileStoreWithNetty |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=19.03.8 Server=19.03.8 Image:yetus/ratis:date2020-04-16 |
| JIRA Issue | RATIS-851 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/1393/RATIS-851.001.patch |
| Optional Tests | dupname asflicense javac javadoc unit findbugs
checkstyle compile |
| uname | Linux f9aa45797466 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19
08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-RATIS-Build/yetus-personality.sh
|
| git revision | master / a1785b7 |
| maven | version: Apache Maven 3.6.3
(cecedd343002696d0abb50b32b541b8a6ba2883f) |
| Default Java | 1.8.0_242 |
| unit |
https://builds.apache.org/job/PreCommit-RATIS-Build/1287/artifact/out/patch-unit-root.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-RATIS-Build/1287/testReport/ |
| Max. process+thread count | 1656 (vs. ulimit of 5000) |
| modules | C: ratis-client U: ratis-client |
| Console output |
https://builds.apache.org/job/PreCommit-RATIS-Build/1287/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> Raft Client should not change leader on ResourceUnavailableException
>
[jira] [Commented] (RATIS-852) GrpcSslTest fails with CertificateExpiredException
[
https://issues.apache.org/jira/browse/RATIS-852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17084577#comment-17084577
]
Hadoop QA commented on RATIS-852:
-
| (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 6s{color}
| {color:red} RATIS-852 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-852 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/13000100/RATIS-852.001.patch |
| Console output |
https://builds.apache.org/job/PreCommit-RATIS-Build/1288/console |
| Powered by | Apache Yetus 0.8.0 http://yetus.apache.org |
This message was automatically generated.
> GrpcSslTest fails with CertificateExpiredException
> --
>
> Key: RATIS-852
> URL: https://issues.apache.org/jira/browse/RATIS-852
> Project: Ratis
> Issue Type: Bug
> Components: thirdparty
>Reporter: Mukul Kumar Singh
>Assignee: Mukul Kumar Singh
>Priority: Major
> Attachments: RATIS-852.001.patch
>
>
> GrpcSslTest fails with CertificateExpiredException
> {code}
> [INFO] Running org.apache.ratis.thirdparty.demo.GrpcSslTest
> 2020-04-16 11:40:30,624 [Thread-0] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/server.pem
> 2020-04-16 11:40:30,624 [main] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/client.pem
> 2020-04-16 11:40:30,627 [Thread-0] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/server.crt
> 2020-04-16 11:40:30,629 [main] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/ca.crt
> 2020-04-16 11:40:30,629 [Thread-0] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/client.crt
> 2020-04-16 11:40:30,630 [main] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/client.crt
> 2020-04-16 11:40:31,224 [Thread-0] INFO demo.GrpcServer
> (GrpcSslServer.java:start(69)) - GrpcSslServer started, listening on 50005
> 2020-04-16 11:40:31,454 [main] WARN demo.GrpcSslClient
> (GrpcSslClient.java:greet(86)) - RPC failed: {0}
> org.apache.ratis.thirdparty.io.grpc.StatusRuntimeException: UNAVAILABLE: io
> exception
> Channel Pipeline: [SslHandler#0, ProtocolNegotiators$ClientTlsHandler#0,
> WriteBufferingAndExceptionHandler#0, DefaultChannelPipeline$TailContext#0]
> at
> org.apache.ratis.thirdparty.io.grpc.stub.ClientCalls.toStatusRuntimeException(ClientCalls.java:235)
> at
> org.apache.ratis.thirdparty.io.grpc.stub.ClientCalls.getUnchecked(ClientCalls.java:216)
> at
> org.apache.ratis.thirdparty.io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:141)
> at
> org.apache.ratis.thirdparty.demo.GreeterGrpc$GreeterBlockingStub.hello(GreeterGrpc.java:156)
> at
> org.apache.ratis.thirdparty.demo.GrpcSslClient.greet(GrpcSslClient.java:82)
> at
> org.apache.ratis.thirdparty.demo.GrpcSslTest.testSslClientServer(GrpcSslTest.java:73)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at
[jira] [Updated] (RATIS-847) Upgrade netty to 4.1.48.Final
[ https://issues.apache.org/jira/browse/RATIS-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mukul Kumar Singh updated RATIS-847: Attachment: RATIS-847.003.patch > Upgrade netty to 4.1.48.Final > - > > Key: RATIS-847 > URL: https://issues.apache.org/jira/browse/RATIS-847 > Project: Ratis > Issue Type: Bug > Components: thirdparty >Reporter: Lokesh Jain >Priority: Major > Attachments: RATIS-847.001.patch, RATIS-847.002.patch, > RATIS-847.003.patch > > > We should upgrade netty version to 4.1.48.Final. We are currently on > 4.1.46.Final -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (RATIS-852) GrpcSslTest fails with CertificateExpiredException
[
https://issues.apache.org/jira/browse/RATIS-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mukul Kumar Singh updated RATIS-852:
Attachment: RATIS-852.001.patch
> GrpcSslTest fails with CertificateExpiredException
> --
>
> Key: RATIS-852
> URL: https://issues.apache.org/jira/browse/RATIS-852
> Project: Ratis
> Issue Type: Bug
> Components: thirdparty
>Reporter: Mukul Kumar Singh
>Assignee: Mukul Kumar Singh
>Priority: Major
> Attachments: RATIS-852.001.patch
>
>
> GrpcSslTest fails with CertificateExpiredException
> {code}
> [INFO] Running org.apache.ratis.thirdparty.demo.GrpcSslTest
> 2020-04-16 11:40:30,624 [Thread-0] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/server.pem
> 2020-04-16 11:40:30,624 [main] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/client.pem
> 2020-04-16 11:40:30,627 [Thread-0] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/server.crt
> 2020-04-16 11:40:30,629 [main] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/ca.crt
> 2020-04-16 11:40:30,629 [Thread-0] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/client.crt
> 2020-04-16 11:40:30,630 [main] INFO demo.GrpcSslTest
> (GrpcSslTest.java:getResource(37)) - Getting Resource:
> /Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/client.crt
> 2020-04-16 11:40:31,224 [Thread-0] INFO demo.GrpcServer
> (GrpcSslServer.java:start(69)) - GrpcSslServer started, listening on 50005
> 2020-04-16 11:40:31,454 [main] WARN demo.GrpcSslClient
> (GrpcSslClient.java:greet(86)) - RPC failed: {0}
> org.apache.ratis.thirdparty.io.grpc.StatusRuntimeException: UNAVAILABLE: io
> exception
> Channel Pipeline: [SslHandler#0, ProtocolNegotiators$ClientTlsHandler#0,
> WriteBufferingAndExceptionHandler#0, DefaultChannelPipeline$TailContext#0]
> at
> org.apache.ratis.thirdparty.io.grpc.stub.ClientCalls.toStatusRuntimeException(ClientCalls.java:235)
> at
> org.apache.ratis.thirdparty.io.grpc.stub.ClientCalls.getUnchecked(ClientCalls.java:216)
> at
> org.apache.ratis.thirdparty.io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:141)
> at
> org.apache.ratis.thirdparty.demo.GreeterGrpc$GreeterBlockingStub.hello(GreeterGrpc.java:156)
> at
> org.apache.ratis.thirdparty.demo.GrpcSslClient.greet(GrpcSslClient.java:82)
> at
> org.apache.ratis.thirdparty.demo.GrpcSslTest.testSslClientServer(GrpcSslTest.java:73)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> at
>
[jira] [Created] (RATIS-852) GrpcSslTest fails with CertificateExpiredException
Mukul Kumar Singh created RATIS-852:
---
Summary: GrpcSslTest fails with CertificateExpiredException
Key: RATIS-852
URL: https://issues.apache.org/jira/browse/RATIS-852
Project: Ratis
Issue Type: Bug
Components: thirdparty
Reporter: Mukul Kumar Singh
Assignee: Mukul Kumar Singh
GrpcSslTest fails with CertificateExpiredException
{code}
[INFO] Running org.apache.ratis.thirdparty.demo.GrpcSslTest
2020-04-16 11:40:30,624 [Thread-0] INFO demo.GrpcSslTest
(GrpcSslTest.java:getResource(37)) - Getting Resource:
/Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/server.pem
2020-04-16 11:40:30,624 [main] INFO demo.GrpcSslTest
(GrpcSslTest.java:getResource(37)) - Getting Resource:
/Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/client.pem
2020-04-16 11:40:30,627 [Thread-0] INFO demo.GrpcSslTest
(GrpcSslTest.java:getResource(37)) - Getting Resource:
/Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/server.crt
2020-04-16 11:40:30,629 [main] INFO demo.GrpcSslTest
(GrpcSslTest.java:getResource(37)) - Getting Resource:
/Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/ca.crt
2020-04-16 11:40:30,629 [Thread-0] INFO demo.GrpcSslTest
(GrpcSslTest.java:getResource(37)) - Getting Resource:
/Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/client.crt
2020-04-16 11:40:30,630 [main] INFO demo.GrpcSslTest
(GrpcSslTest.java:getResource(37)) - Getting Resource:
/Users/mukul/code/apache/ratis/thirdparty/test/target/test-classes/ssl/client.crt
2020-04-16 11:40:31,224 [Thread-0] INFO demo.GrpcServer
(GrpcSslServer.java:start(69)) - GrpcSslServer started, listening on 50005
2020-04-16 11:40:31,454 [main] WARN demo.GrpcSslClient
(GrpcSslClient.java:greet(86)) - RPC failed: {0}
org.apache.ratis.thirdparty.io.grpc.StatusRuntimeException: UNAVAILABLE: io
exception
Channel Pipeline: [SslHandler#0, ProtocolNegotiators$ClientTlsHandler#0,
WriteBufferingAndExceptionHandler#0, DefaultChannelPipeline$TailContext#0]
at
org.apache.ratis.thirdparty.io.grpc.stub.ClientCalls.toStatusRuntimeException(ClientCalls.java:235)
at
org.apache.ratis.thirdparty.io.grpc.stub.ClientCalls.getUnchecked(ClientCalls.java:216)
at
org.apache.ratis.thirdparty.io.grpc.stub.ClientCalls.blockingUnaryCall(ClientCalls.java:141)
at
org.apache.ratis.thirdparty.demo.GreeterGrpc$GreeterBlockingStub.hello(GreeterGrpc.java:156)
at
org.apache.ratis.thirdparty.demo.GrpcSslClient.greet(GrpcSslClient.java:82)
at
org.apache.ratis.thirdparty.demo.GrpcSslTest.testSslClientServer(GrpcSslTest.java:73)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
Caused by:
