qwtsc opened a new issue, #2355: URL: https://github.com/apache/incubator-hugegraph/issues/2355
### Problem Type (问题类型) None ### Before submit - [X] 我已经确认现有的 [Issues](https://github.com/apache/hugegraph/issues) 与 [FAQ](https://hugegraph.apache.org/docs/guides/faq/) 中没有相同 / 重复问题 (I have confirmed and searched that there are no similar problems in the historical issue and documents) ### Environment (环境信息) hugegraph with the master branch ### Your Question (问题描述) I recently reviewed the hugegraph code base in detail. One thing confused me a lot is the master/slave design. It seems to use to schedule the async task to the whole cluster, but in the meanwhile it's also used to redirect the schema create/update/delete and gremlin api to master endpoint. It looks like that if we do the schema update in only one node (that is master node) then we can ensure the concurrent safety in the whole cluster without any distributed lock's help. if the above reasoning makes sense, why don't we need redirectMasterRole annotation in VertexApi and EdgeApi when doing modification to vertex and edge? Is it a bug or just by design? ### Vertex/Edge example (问题点 / 边数据举例) _No response_ ### Schema [VertexLabel, EdgeLabel, IndexLabel] (元数据结构) _No response_ -- 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: dev-unsubscr...@hugegraph.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
