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.

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

Query about Jdempotent States #34

Open
IOhacker opened this issue Nov 24, 2021 · 1 comment
Open

Query about Jdempotent States #34

IOhacker opened this issue Nov 24, 2021 · 1 comment

Comments

@IOhacker
Copy link

Jdempotent supports the following states and conditions?

  1. unlocked - lock doesn't exist and can be locked
    locked - lock exists and is used by a process to guard a write
    i. typically we set a ttl on the lock according to the amount of time the write would take
    ii. i.e. DB write in JTA transaction of 120 seconds would use a 120 second ttl
    iii. if the lock doesn't transition to failed/committed in this time the lock is expired
  2. expired - lock expired TTL (vm, jvm, thread error)
    i. a retry can transition this from expired to locked
  3. failed - the owning process released with error (no DB connection, etc)
    i. a retry can transition this from failed to locked
  4. committed - write process completed all work, this is an immutable state
@memojja
Copy link
Contributor

memojja commented Dec 10, 2021

Now jdempotent has not locking system, but it will be good. i will get this task to backlog

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants