[
https://issues.apache.org/jira/browse/RATIS-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17084485#comment-17084485
]
Hanisha Koneru edited comment on RATIS-850 at 4/16/20, 2:17 AM:
----------------------------------------------------------------
Fixed the checkstyle and one related failing unit test -
_ratis.conf.TestConfUtils_ in Patch v02.
The following unit tests are failing in master too:
* ratis.logservice.server.TestMetaServer
* ratis.server.simulation.TestRaftWithSimulatedRpc
* ratis.server.simulation.TestRaftSnapshotWithSimulatedRpc
* ratis.netty.TestRaftSnapshotWithNetty
* ratis.grpc.TestRaftSnapshotWithGrpc
The other unit tests reported are passing locally.
was (Author: hanishakoneru):
Fixed the checkstyle and one related failing unit test -
_ratis.conf.TestConfUtils_ in Patch v02.
The following unit tests are failing in master too:
* ratis.logservice.server.TestMetaServer
* ratis.server.simulation.TestRaftWithSimulatedRpc
* ratis.server.simulation.TestRaftSnapshotWithSimulatedRpc
* ratis.netty.TestRaftSnapshotWithNetty
* ratis.grpc.TestRaftSnapshotWithGrpc
The other unit tests reported are passing locally.
> Allow log purge up to snapshot index
> ------------------------------------
>
> Key: RATIS-850
> URL: https://issues.apache.org/jira/browse/RATIS-850
> Project: Ratis
> Issue Type: Improvement
> Reporter: Hanisha Koneru
> Assignee: Hanisha Koneru
> Priority: Major
> Attachments: RATIS-850.001.patch, RATIS-850.002.patch
>
>
> Ratis logs are purged only up to the least commit index on all the peers. But
> if one peer is down, it stop log purging on all the peers. If the Ratis
> server takes snapshots, then we can purge logs up to the snapshot index even
> if some peer has not committed up to that index. When the peer rejoins the
> ring, instead of ratis logs, it can get the snapshot to catch up.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
