-
Bug
-
Resolution: Fixed
-
Low (View bug fix roadmap)
-
8.13.0, 8.20.0, 8.22.0, 8.20.10, 9.4.16, 9.4.17
-
None
-
8.13
-
12
-
Severity 3 - Minor
-
3
-
Issue Summary
This is reproducible on Data Center: yes
In DVCS there are two jobs. First one is sync job which synchronize organizations in every hour. Second one is a job which adds repositories to newly added organization. The problem is that both jobs use the same cluster lock com.atlassian.jira.plugins.dvcs.service.RepositoryService.syncRepositoryList. It may happen that second job won’t start because first job is in progress and holds lock.
Steps to Reproduce
- Hourly job should be in progress. When it starts and how long it runs you can check here:
- ⚙ -> System -> Scheduled details
- Search for “com.atlassian.jira.plugins.dvcs.scheduler.DvcsScheduler” click "Show more"
- You should see similar details:
- Add new organization on DVCS admin panel.
Expected Results
Organization should be added and should have all repositories.
Actual Results
Organization is added to DVCS but without repositories:
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- follows
-
JSWSERVER-14061 Long running synchronization initiation blocks subsequent scheduled syncs and other scheduled tasks
-
- Closed
-
- is related to
-
JSWSERVER-21230 Repositories are not sync during adding a new organisation
-
- Closed
-
- relates to
-
JSWSERVER-14061 Long running synchronization initiation blocks subsequent scheduled syncs and other scheduled tasks
-
- Closed
-
- blocks
-
PSR-908 You do not have permission to view this issue
- is duplicated by
-
FLASH-4140 You do not have permission to view this issue
- is resolved by
-
JAPPSS-5 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
Form Name |
---|
Our team have encountered this bug in our instance and it is having a significant impact on our operations. The details of the bug align closely with our experience, causing considerable disruption in our workflow.
Jira version: 9.4.12
Jira DVCS Connector Plugin version: 5.11.14