redis_queued_locks 1.8.0 → 1.9.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7f8dd117ee12f1f598da555d02516bb950a2d9640b075a048612726b7a88a6ad
-  data.tar.gz: c0a5ac4a4dcb6f3b448dc23ffa8d0e0e13a726d50bdd98fc40193704aa6f967d
+  metadata.gz: f787fbfe22ef8fe8dec78e5b17d4305621a4b9e2df7d3582648959e68dabef09
+  data.tar.gz: 8d874d80738959f41985e6e52d6668aa63d8232ca4964006be82f5d67ea7e1a6
 SHA512:
-  metadata.gz: b35d0ef98da0e1ec2c2368b36064eb0501b45d26aaa1b7204230692a41025583366ce181b85eec09cff2d6fe4e93ec146280db78e08f8cbb232a559b91f6d489
-  data.tar.gz: 4776dd89a7bf1e27476877465faf3240988929efe398090fa4b8b4f604a976a861558e6f606278b91c2c95530be6c5205f8245c887befe92a75d4efde31820dc
+  metadata.gz: eb726c270398079b142d68e3e45dd93226e1f17b52f370107db2f4cc47bfa6b0ce010f55dec029443bfb932d73f905f61040087577f47dca9cef5ad505fca430
+  data.tar.gz: 129089ba8f764ecabae8d0598af0f627a1156bb8b1a3e845697f1f32863d7ccd3eb2cd64cb80406408e8518b9809b35cce36e1253598744d52529d32cb092598

data/.ruby-version

@@ -1 +1 @@
-3.1.2
+3.3.3

data/CHANGELOG.md

@@ -1,5 +1,56 @@
 ## [Unreleased]
 
+## [1.9.0] - 2024-07-15
+### Added
+- Brand New Extremely Major Feature: **Swarm Mode** - eliminate zombie locks with a swarm:
+  - works by `supervisor` + `actor model` abstractions;
+  - all your ruby workers can become an element of the processs swarm;
+  - each ruby worker of the swarm probes himself that he is alive;
+  - worker that does not probes himselfs treats as a zombie;
+  - worekr becomes dead when your ruby process is dead, or thread is dead or your ractor is dead;
+  - each zombie's lock, acquier and position in queue are flushed in background via `flush_zombies` swarm element;
+  - the supervisor module keeps up and running each swarm melement (`probe_hosts` and `flush_zombies`):
+    - cuz each element works in background and can fail by any unexpected exception the supervisor guarantees that your elements will ressurect after that;
+  - each element can be deeply configured (and enabled/disabled);
+  - abilities:
+    - configurable swarming and deswarming (`#swarmize!`, `#deswarmize!`);
+    - encapsulated swarm interface;
+    - two fully isolated swarm elements: `probe_hosts` and `flush_zombies`;
+    - supervisor that keeps all elements running and wokring;
+    - an ability to check the swarm status (`#swarm_status`): who is working, who is dead, running status, internal main loop states, etc;
+    - an abiltiy to check the swarm information (`#swarm_info`): showing the current swarm hosts and their last probes and current zombie status;
+    - an ability to find zombie locks, zombie acquiers and zombie hosts (`#zombie_locks`, `#zombie_acquiers`, `#zombie_hosts`);
+    - an ability to extract the full zombie information (`#zombies_info`/`#zombies`);
+    - each zombie lock will be flushed in background by appropriated swarm element (`flush_zombies`);
+    - deeply configurable zombie factors: zombie ttl, host probing period, supervisor check period;
+    - an ability to manually probe hosts;
+    - an ability to flush zombies manually;
+    - you can made `swarm`-based logic by yourself (by manually runnable `#flush_zombies` and `#probe_hosts`);
+  - summarized interface:
+    - `#swarmize!`, `#deswarmize!`;
+    - `#swarm_status`/`#swarm_state`, `#swarm_info`
+    - `#zombie_locks`, `#zmobie_acquiers`, `#zombie_hosts`, `#zombies_info`/`#zombies`;
+    - manual abilities: `#probe_hosts`, `#flush_zombies`;
+  - **general note**: each swarm element should have their own `RedisClient` instance so each have their own redis-client configuration
+    and each of the can be configured separately (**RedisClient** multithreading limitation and **Ractor** limitations);
+- Added the `lock host` abstraction (`hst_id`):
+  - each lock is hosted by some ruby workers so this fact is abstracted into the host identifier represended as a combination of `process_id`/`thread_id`/`ractor_id`/`uniq_identity`;
+  - the ruby worker is a combination of `process_id`/`thread_id`/`ractor_id`/`uniq_identity`);
+  - each lock stores the host id (`hst_id` field) indisde their data (for debugging purposes and zombie identification purposes);
+  - every lock information method now includes `hst_id` field: `#lock_info`, `#lock_data`, `#locks_info`;
+  - an ability to fetch the current host id (your ruby worker host id): `#current_host_id`;
+  - an ability to fetch all possible host ids in the current Ractor (all possible and reachable ruby workers from the current ractor): `#possible_host_ids`;
+  - extended `RedisQueuedLocks::TimedLocktimeoutError` message: added `hst_id` field data from the lock data;
+- **Instrumentation** updates:
+  - added the `hst_id` field to each locking-process-related instrumentation event;
+- **Logging** updates:
+  - added `hst_id` field to each locking-process-related log;
+- **Logging/Instrumentation Sampling** updates:
+  - an ability to mark any loggable/instrumentable method as sampled for instrumentation/logging despite of the enabled instrumentation/log sampling
+    by providing the `log_sample_this: true` attribute and `instr_sample_this: true` attribute respectively;
+- an alias for `#clear_locks`: `#release_locks`;
+- an alias for `#unlock`: `#release_lock`;
+
 ## [1.8.0] - 2024-06-13
 ### Added
 - A configurable option that enables the adding additional lock/queue data to "Acquirement Timeout"-related error messages for better debugging;