PullRequestRescopeBucketProcessor Rescheduled rescope processing for large number of repositories getting logged in Bitbucket Server
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
You might see "PullRequestRescopeBucketProcessor Rescheduled rescopes processing" for a large number of repositories is getting logged while restarting the Bitbucket Service.
1
2
3
4
5
6
7
8
INFO [spring-startup] c.a.s.i.p.r.PullRequestRescopeBucketProcessor Rescheduled rescope processing for 204 repositories:
INFO [spring-startup] c.a.s.i.p.r.PullRequestRescopeBucketProcessor Rescheduled rescope processing for 3796 repositories
INFO [spring-startup] c.a.s.i.p.r.PullRequestRescopeBucketProcessor Rescheduled rescope processing for 1600 repositories:
INFO [spring-startup] c.a.s.i.p.r.PullRequestRescopeBucketProcessor Rescheduled rescope processing for 249 repositories:
INFO [spring-startup] c.a.s.i.p.r.PullRequestRescopeBucketProcessor Rescheduled rescope processing for 417 repositories:
INFO [spring-startup] c.a.s.i.p.r.PullRequestRescopeBucketProcessor Rescheduled rescope processing for 177 repositories
INFO [spring-startup] c.a.s.i.p.r.PullRequestRescopeBucketProcessor Rescheduled rescope processing for 417 repositories
INFO [spring-startup] c.a.s.i.p.r.PullRequestRescopeBucketProcessor Rescheduled rescope processing for 177 repositories:What does this mean and does its impact the performance of the BItbucket server?
Solution
There's nothing one should be worried about at the moment regarding their Pull Requests.
1
INFO [spring-startup] c.a.s.i.p.r.PullRequestRescopeBucketProcessor Rescheduled rescope processing for 204 repositories:
The rescheduling happens only during a startup of the nodes. This is done for all the repositories that have been scheduled to perform the Pull Request rescoping during the time a node was down. Once you bring a node up, it checks which repositories have to run a rescope and schedules it. There's no action on the admin/user side, everything has been taken care of by Bitbucket.
The only situation when you should be concerned about a large volume of repositories scheduled for a rescoping is the time when the log entry is followed by hundreds of other entries occurrences over the course of few hours that says:
1
No chain builders available for processing
which means there were not enough chain builders for Pull Requests rescoping, which usually manifests performance issues.
Was this helpful?