Hi,
In current code, while flushing AST, we don't handle an exception that
sending AST or BAST is failed.
But it is indeed possible that AST or BAST is lost due to some kind of
networks fault.
If above exception happens, the requesting node will never obtain an AST
back, hence, it will never acqu
Base on your description, this case should be a corner case, NOT a fatal error.
Should we use mlog(ML_NOTICE, ...) to print these logs?
Thanks
Gang
>>>
> Hi,
>
> In current code, while flushing AST, we don't handle an exception that
> sending AST or BAST is failed.
> But it is indeed possible
Hi Gang,
At present time, when AST or BAST sending is failed, it already prints
ERROR logs.
I admit that it's truly a corner case but a fatal error when networks is
not reliable.
Because if AST is not sent back to locking node, related procedure will
be pending, even the whole cluster will hang.
On Mon, Aug 7, 2017 at 2:13 AM, Changwei Ge wrote:
> Hi,
>
> In current code, while flushing AST, we don't handle an exception that
> sending AST or BAST is failed.
> But it is indeed possible that AST or BAST is lost due to some kind of
> networks fault.
>
> If above exception happens, the reques
