klion26 commented on PR #3567: URL: https://github.com/apache/amoro/pull/3567#issuecomment-2972193272
> > Sorry for jumping in this late. > > After this change, will there be two Amoro servers handle the same table update(`put`/`post` etc rest) logic? If this is yes, will this lead to some wrong result/state? > > Optimization services will not be processed simultaneously, we ensure that only one master node handles Optimizer. Other child nodes can handle Rest requests, such as creating and deleting catalogs. Will this have an impact? As there is more than one server that will update the same table's info/state, we need to handle this carefully to avoid the inconsistent state of concurrent modification. Maybe we need to add a doc to analysis this -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
