Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gateway: Internal refactoring, requires manual upgrade when using fs gateway #232

Closed
kimchy opened this issue Jun 21, 2010 · 3 comments

Comments

Projects
None yet
2 participants
@kimchy
Copy link
Member

commented Jun 21, 2010

A comprehensive refactoring in the gateway module, allowing for easier implementation of other different types as well as more code reuse. Also, this is the first step at getting to reuse the work directory when possible.

When using the FS gateway, and upgrade to 0.9 requires location the matedata-XXX files, creating a directory called metadata in the same location, and moving the metadata-XXX files there.

@kimchy

This comment has been minimized.

Copy link
Member Author

commented Jun 21, 2010

Gateway: Internal refactoring, requires manual upgrade when using fs gateway, closed by 7ed7c6d.

@clintongormley

This comment has been minimized.

Copy link
Member

commented Jun 21, 2010

kimchy - could you give a real example. It's not very clear from the description. btw, sounds like a real win!

@kimchy

This comment has been minimized.

Copy link
Member Author

commented Jun 22, 2010

Sure, so, if you configure a gateway path to /mnt/test, you will find metadata- files within a sub directory named after the cluster name: /mnt/test/[cluster_name]. Upgrading to version 0.9 requires to take those metadata- files, and placing them under the /mnt/test/[cluster_name]/metadata/.

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.