LuQQiu
commented
3 years ago According to @maobaolong, the benefits of this change includes:
- support job master leadership transition
- Client better know the transfer leadership related error/exceptions: The current status is the leading master send transfer leadership request to ratis server asynchronously, client doesn't know the exception and error during the leadership transfer, and can only know that the transfer timeout. When putting to the client-side, client side can finish the transfer leadership in its process and know whether the request error put or timeout, so that electCommand can give user the error message and exit earlier
@jenoudet @ggezer any ideas of whether putting into client-side is beneficial or not? what are your concerns about moving from master to client-side? @apc999 FYI
maobaolong
ggezer
Is your feature request related to a problem? Please describe.
Now, alluxio master like a remote proxy for alluxio elect shell from client side, which send transferleader rpc to ratis server asynchronously, so the elect shell will not receive any message although the transferleader rpc call timeout or encountered an exception
If we move the tranfer leadership code logic from master to the client-side, we can maintain the progress, status, result easily.
Describe the solution you'd like
Describe alternatives you've considered
let admin shell trigger transfer leader.
Urgency
Normal
Additional context
No