error remaping lock file in classic server [CORE2062] #2498
Assignees
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Modified by: @AlexPeshkoffVersion: 2.5 Alpha 1 [ 10224 ] |
|
Commented by: @AlexPeshkoff remap_local_owners() is called when owner (and process) are not created with m_processOffset == 0. This is not assertion point - just do not notify anyone if there is anyway no process (and therefore no owners) to notify. |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5 Beta 1 [ 10251 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: No test => Cannot be tested |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: @AlexPeshkoff
When new process starts, it initially maps only default size of lock file, which may be smaller then actually used by all others. If owner that should be created happens to be placed at location greater than default size of lock file (which is quite possible if other processes are already working actively), call to remap_local_owners() takes place with DUMMY_OWNER. This leads to various inconsistencies in lock manager (hangs, AVs, may be something else).
Commits: 97f89cb
The text was updated successfully, but these errors were encountered: