[Store] config: start http server from master

[stmatengss]

No description provided.

[xiaguan]

Would a std::optionalstd::string suffice for this case?

[stmatengss]

Would a std::optionalstd::string suffice for this case?

Sure

[ykwd]

Could you clarify why the metadata server needs to be started in the master process?

[stmatengss]

Could you clarify why the metadata server needs to be started in the master process?

It will make deployment easier. By the way, as future work, we can make the HTTP metadata server more robust using master's high-availability protocol.

[ykwd]

Could you clarify why the metadata server needs to be started in the master process?

It will make deployment easier. By the way, as future work, we can make the HTTP metadata server more robust using master's high-availability protocol.

Could you elaborate a bit more on why this makes deployment easier? From what I can see, the master process is only running a bash command like:

python3 -m mooncake.http_metadata_server --args...

It seems this could just as well be executed directly from a deployment script. In fact, in some cases, this would be more flexible.

Also, since the metadata server already supports etcd, and given that master high availability also relies on etcd, wouldn’t it make sense to simply use the etcd metadata server directly?

[stmatengss]

Could you clarify why the metadata server needs to be started in the master process?

It will make deployment easier. By the way, as future work, we can make the HTTP metadata server more robust using master's high-availability protocol.

Could you elaborate a bit more on why this makes deployment easier? From what I can see, the master process is only running a bash command like:

python3 -m mooncake.http_metadata_server --args...

It seems this could just as well be executed directly from a deployment script. In fact, in some cases, this would be more flexible.

Also, since the metadata server already supports etcd, and given that master high availability also relies on etcd, wouldn’t it make sense to simply use the etcd metadata server directly?

It simply offers a convenient way to deploy the Mooncake master and metadataserver together. We can also include etcd as an optional component. I suggest adding a new parameter to enable more flexible deployment. Or we can use a c++ based http server on the master side?