[
https://issues.apache.org/jira/browse/CASSANDRA-11258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15242932#comment-15242932
]
Marcus Olsson commented on CASSANDRA-11258:
-------------------------------------------
I've pushed a rebased patch where I addressed your two comments from github
(the comments got lost in the rebase so should I avoid rebase until review is
done in the future?). I also added a removal of the locked resource when the
lock object is closed.
Regarding my previous comment I'm starting to think it would be cleaner(for the
code using the locks at least) to have the implementation the way Java locks
are used instead.
> 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)
