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

provide option for storing offsets in s3 instead of zookeeper #106

Open
joestein opened this issue May 15, 2015 · 2 comments
Open

provide option for storing offsets in s3 instead of zookeeper #106

joestein opened this issue May 15, 2015 · 2 comments

Comments

@joestein
Copy link
Contributor

No description provided.

@marcusking01
Copy link
Contributor

Storing offsets in S3 may not be a great idea due to the lack of strong consistency, and could result in the same offset being vended multiple times.

@joestein
Copy link
Contributor Author

The person that brought it up had mention they were looking to use http://docs.basho.com/riakcs/latest/references/apis/storage/s3/ as way to plug it in.

Before we would even do this we would do this but providing the plug-able interface for zookeeper both for consensus and offset storage is important. Probably after siesta gets tested to replace sarama.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants