[
https://issues.apache.org/jira/browse/HDDS-14425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-14425:
-------------------------------
Description:
It might be possible for Ratis to throw ReadIndexException if the follower is
not able to get the ReadIndex one way or another (e.g. majority OMs are down).
Additionally ReadException will be thrown for any pending requests. However,
currently this is not handled by both the OM server and client.
OM need to throw these exceptions to prevent NPE similar to HDDS-10918. Client
can parse these exceptions and log it.
was:
It might be possible for Ratis to throw ReadIndexException if the follower is
not able to get the ReadIndex one way or another (e.g. majority OMs are down).
Additionally ReadException will be thrown for any pending requests. However,
currently this is not handled by both the OM server and client.
We need to throw this to prevent NPE similar to HDDS-10918.
> Implement Ratis follower read exception handling
> ------------------------------------------------
>
> Key: HDDS-14425
> URL: https://issues.apache.org/jira/browse/HDDS-14425
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ivan Andika
> Assignee: Ivan Andika
> Priority: Major
>
> It might be possible for Ratis to throw ReadIndexException if the follower is
> not able to get the ReadIndex one way or another (e.g. majority OMs are
> down). Additionally ReadException will be thrown for any pending requests.
> However, currently this is not handled by both the OM server and client.
> OM need to throw these exceptions to prevent NPE similar to HDDS-10918.
> Client can parse these exceptions and log it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
