pulsar
pulsar copied to clipboard
apache
Is it possible to migrate from zookeeper metadata store to etcd?
What issue do you find in Pulsar docs?
New 2.10.0 pulsar now supported ETCD as metadata store and we would like to migrate current zookeeper to etcd. Is it possible and is there any guidlines existed? Downtime should be acceptable :D
What is your suggestion?
Provide metadatastore migration documents or a tool for doing it.
Do you have any references?
Nope
Would you like to fix this issue?
Nope
Note
- [X] I have researched my question.
Checked this issue with @nodece - it is not supported to migrate exiting metadata from ZooKeeper to ETCD.
@truong-hua Thanks for raising this issue! Does the answer LGTY? Feel free to close this issue if you have more questions.
I suggest add documentation on how to switch the metadata store from ZK to ETCD/Memory/RockDB.
I suggest add documentation on how to switch the metadata store from ZK to ETCD/Memory/RockDB.
Agree. Pulsar will be more portable and less depended on metadata store if we can do it.
I suggest add documentation on how to switch the metadata store from ZK to ETCD/Memory/RockDB.
Make sense. @nodece can you provide more inputs?
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
@momo-jun there is a new doc to config etcd as metadata store but there is no document for migrating from a key-value store to another. So this issue is not closed yet.
@truong-hua Yes, the new doc is config etcd as metadatastore, right now we don't support migrating the data from one metadatastore to another.
So this issue should not be closed @momo-jun @nodece. Btw, if we can have a document about data structure or scheme of our current metadata on ZK and ETCD. May be people can think about migrating themselves manually, or may be some one can make a tool?
So this issue should not be closed
No. This can be closed as won't do. They're totally different storage backends. Such data migration should not be implemented in the Pulsar scope.
Keeping an issue open doesn't mean that it will be implemented. We generally use issues to track actionable tasks, not a wishing list. If an optional improvement doesn't have a concrete proposal and no contributor works on it, it's valueless to keep it open.
@tisonkun can this one be consider as to provide zookeeper metadata scheme structure doc and other like etcd. So the user can try themself to migrate it. I can not do it without deeply knowledge about the metadata scheme. A document about that would help.