Skip to content
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

Locking service #140

Open
tshemsedinov opened this issue Aug 1, 2018 · 2 comments
Open

Locking service #140

tshemsedinov opened this issue Aug 1, 2018 · 2 comments

Comments

@tshemsedinov
Copy link
Member

tshemsedinov commented Aug 1, 2018 •
edited
Loading

  • We allow entity-level locking, so locking should be registered on entity master server (according to the routing, server Id will be extracted from entity Id by server suffix mask)
  • Table Identifier have a field Lock of enumerated type Enum('Free', 'Locked') See: System table: Identifier #151
  • Locking service should have queue for exclusive entity access
  • Locking service should have configurable timeout
  • Special permission for locking is a permission for certain entity
  • Long locking with auto unlock
  • Restore lock if it is overdue but object is not changed
@tshemsedinov tshemsedinov changed the title Implement alternative validation without reinstantiation Implement locking service Aug 1, 2018
@tshemsedinov
Copy link
Member Author

  • Now field lock is a timestamp (nullable), if it is not null we have a lock.
  • User account which started lock will be specified in memory lock table in that certain server where locked record is suitable by Id suffix (record master server).

@tshemsedinov
Copy link
Member Author

  • LockedBy: { domain: 'SID' } stores Session identifier in chain stores User identifier

@tshemsedinov tshemsedinov changed the title Implement locking service Locking service Sep 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tshemsedinov