Skip to content

Ability to configure sleep Time in JdbcLockRegistry #3010

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
gurudatta11 opened this issue Jul 26, 2019 · 0 comments · Fixed by #3039
Closed

Ability to configure sleep Time in JdbcLockRegistry #3010

gurudatta11 opened this issue Jul 26, 2019 · 0 comments · Fixed by #3039
Assignees
@artembilan
Labels
in: jdbc type: enhancement
Milestone
5.1.8

Comments

@gurudatta11
Copy link

gurudatta11 commented Jul 26, 2019 •
edited
Loading

In clustered environment, the Non leader nodes tries for lock too frequently (100ms).
Can we enhance it to be configurable property either from constructor or property value in
org.springframework.integration.jdbc.lock.JdbcLockRegistry
@garyrussell garyrussell added this to the 5.1.7 milestone Jul 27, 2019
@garyrussell garyrussell modified the milestones: 5.1.7, Backlog, 5.1.8 Aug 5, 2019
@artembilan artembilan self-assigned this Aug 19, 2019
artembilan added a commit to artembilan/spring-integration that referenced this issue Aug 19, 2019
@artembilan
spring-projectsGH-3010 Add idleBetweenTries for JdbcLockRegistry
bd52834 
Fixes spring-projects#3010

Sometimes `100` milliseconds interval is too often to try to obtain a
lock with `UPDATE/INSERT` queries

**Cherry-pick to 5.1.x**
@artembilan artembilan mentioned this issue Aug 19, 2019
Merged
garyrussell pushed a commit that referenced this issue Aug 20, 2019
@artembilan @garyrussell
GH-3010 Add idleBetweenTries for JdbcLockRegistry
f600361 
Fixes #3010

Sometimes `100` milliseconds interval is too often to try to obtain a
lock with `UPDATE/INSERT` queries

**Cherry-pick to 5.1.x**
garyrussell pushed a commit that referenced this issue Aug 20, 2019
@artembilan @garyrussell
GH-3010 Add idleBetweenTries for JdbcLockRegistry
c9e0cc0 
Fixes #3010

Sometimes `100` milliseconds interval is too often to try to obtain a
lock with `UPDATE/INSERT` queries

**Cherry-pick to 5.1.x**
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@artembilan artembilan

Labels
in: jdbc type: enhancement
Projects
None yet
Milestone
5.1.8
Development

Successfully merging a pull request may close this issue.

GH-3010 Add idleBetweenTries for JdbcLockRegistry artembilan/spring-integration
3 participants
@garyrussell @artembilan @gurudatta11