[MGNLSCH-25] It should be possible to run a job on a single node of the cluster without forcing the node id. Created: 21/Feb/12 Updated: 18/Feb/16 Resolved: 18/Feb/16 |
|
| Status: | Closed |
| Project: | Scheduler |
| Component/s: | None |
| Affects Version/s: | 1.4.3 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Danilo Ghirardelli | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Patch included: |
Yes
|
||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||
| Date of First Response: | |||||||||||||
| Description |
|
I'm opening a new issue to avoid losing a problem discussed in
The first use case is the current behaviour. The other behaviour is not completely covered by the clusterId, but I think it could be done using Jackrabbit cluster-wise locks, just like in the AbstractClusterLockCommand.java class attached. The node on which the job will run is not forced, just the first one that gets the lock is the one that will run the job, the others will quietly skip. |
| Comments |
| Comment by Michael Mühlebach [ 18/Feb/16 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |