Azure / Azure/elastic-db-tools
Explicitly release applock at the end of shard map manager operations
Open
- Dominant language
- C#
- Stars
- 147
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
ShardMapManager library is opening connections with session level applock. There is no explicit call to release the applock, its relying on auto-release as a by product of connection close events, this is not working correctly in case of connection pooling.
Modify the code to explicitly release applocks from library at the end of ShardMapManager operations.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.