[
https://issues.apache.org/jira/browse/HDDS-3227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ethan Rose updated HDDS-3227:
-----------------------------
Target Version/s: 1.3.0 (was: 1.2.0)
I am managing the 1.2.0 release and we currently have more than 600 issues
targeted for 1.2.0. I am moving the target field to 1.3.0.
If you are actively working on this jira and believe this should be targeted
for the 1.2.0 release, Please reach out to me via Apache email or Slack.
> Ensure eviction of stateMachineData from cache only when both followers catch
> up
> --------------------------------------------------------------------------------
>
> Key: HDDS-3227
> URL: https://issues.apache.org/jira/browse/HDDS-3227
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Datanode
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Major
> Labels: Triaged, pull-request-available
>
> Currently, the data in the StateMachineCache is evicted as soon as the
> applyTransaction call is issued for a transaction in Ratis. In our testing
> with keys in few kbs of size, it was figured that the data is evicted from
> the cache before append requests can be processed in a slightly slow follower
> thereby making leader read the chunk data from underlying fs/disk very
> frequently. This leads to slowing down the leader as well as well as overall
> throughput of the pipeline.
> The idea here is to ensure the data is evicted from the cache only when both
> followers have caught up with the match index. If a follower is really slow,
> it will eventually be marked slow after nodeFailureTimeout and pipeline will
> be destroyed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
