[
https://issues.apache.org/jira/browse/CASSANDRA-11258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262374#comment-15262374
]
Marcus Olsson commented on CASSANDRA-11258:
-------------------------------------------
bq. The only thing I mildly dislike about the interfaces is that they throw
exception when it's not possible to acquire or renew the lock, but since this
is quite a common case should we use Optional and boolean instead? WDYT about
this definition?
Sounds good, it seems cleaner to use Optional and booleans instead of
exceptions. :)
I've pushed a new commit
[here|https://github.com/emolsson/cassandra/commits/CASSANDRA-11258].
> Repair scheduling - Resource locking API
> ----------------------------------------
>
> Key: CASSANDRA-11258
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11258
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Marcus Olsson
> Assignee: Marcus Olsson
> Priority: Minor
>
> Create a resource locking API & implementation that is able to lock a
> resource in a specified data center. It should handle priorities to avoid
> node starvation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
