[ML] Add OpAddEntry to pendingAddEntries after the state check #12570
Conversation
- when the state was Fenced, Terminated or Closed, the OpAddEntry instance would remain in pendingAddEntries although the operation is failed immediately.
lhotari
requested review from
merlimat,
rdhabalia,
eolivelli and
codelipenghui
|
@lhotari:Thanks for your contribution. For this PR, do we need to update docs? |
|
@lhotari:Thanks for your contribution. For this PR, do we need to update docs? |
1 similar comment
|
@lhotari:Thanks for your contribution. For this PR, do we need to update docs? |
|
@lhotari:Thanks for providing doc info! |
|
@lhotari One consequence of this issue is that messages can be delivered out-of-order in some scenarios. Is that correct? |
- when the state was Fenced, Terminated or Closed, the OpAddEntry instance would remain in pendingAddEntries although the operation is failed immediately. (cherry picked from commit 409239c)
…e#12570) - when the state was Fenced, Terminated or Closed, the OpAddEntry instance would remain in pendingAddEntries although the operation is failed immediately.
- when the state was Fenced, Terminated or Closed, the OpAddEntry instance would remain in pendingAddEntries although the operation is failed immediately. (cherry picked from commit 409239c)
- when the state was Fenced, Terminated or Closed, the OpAddEntry instance would remain in pendingAddEntries although the operation is failed immediately. (cherry picked from commit 409239c)
- when the state was Fenced, Terminated or Closed, the OpAddEntry instance would remain in pendingAddEntries although the operation is failed immediately. (cherry picked from commit 409239c)
Motivation
instance would remain in pendingAddEntries although the operation is failed
immediately.
Modifications