[
https://issues.apache.org/jira/browse/WHIRR-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045373#comment-13045373
]
Andrei Savu commented on WHIRR-329:
-----------------------------------
I believe this is not that easy:
* http://www.quora.com/How-can-I-implement-optimistic-locking-for-S3-objects
* http://stackoverflow.com/questions/3431418/locking-with-s3
How about using an existing ZooKeeper cluster for this feature? We could put
the quorum address in config and also add a ZooKeeper based cluster state
persistence option.
> Ensure the same cluster can't be started twice
> ----------------------------------------------
>
> Key: WHIRR-329
> URL: https://issues.apache.org/jira/browse/WHIRR-329
> Project: Whirr
> Issue Type: Improvement
> Reporter: Andrei Savu
>
> We should add some sort of distributed locking mechanism so that we can be
> sure that the same cluster can't be started twice. Tibor was the first one to
> raise this issue.
> Could a blobstore be used for locking?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira