Metadata-Version: 2.4
Name: dflockd
Version: 0.4.1
Summary: A lightweight distributed lock server using a simple line-based TCP protocol with FIFO ordering, automatic lease expiry, and background renewal.
Author: Matth Ingersoll
Author-email: Matth Ingersoll <matth@mtingers.com>
License-Expression: MIT
Requires-Dist: pytest-asyncio>=1.3.0 ; extra == 'dev'
Requires-Dist: pytest-cov>=7.0.0 ; extra == 'dev'
Requires-Dist: pyright>=1.1 ; extra == 'dev'
Requires-Python: >=3.13
Project-URL: Homepage, https://github.com/mtingers/kompoz
Project-URL: Repository, https://github.com/mtingers/kompoz
Project-URL: Documentation, https://mtingers.github.io/kompoz/
Project-URL: Bug Tracker, https://github.com/mtingers/kompoz/issues
Project-URL: Changelog, https://github.com/mtingers/kompoz/blob/main/CHANGELOG.md
Provides-Extra: dev
Description-Content-Type: text/markdown

# dflockd

<!--toc:start-->
- [dflockd](#dflockd)
  - [Quick start](#quick-start)
  - [Server configuration](#server-configuration)
  - [CLI arguments](#cli-arguments)
  - [Protocol](#protocol)
    - [Commands](#commands)
    - [Behavior](#behavior)
  - [Client usage](#client-usage)
    - [Async client](#async-client)
    - [Sync client](#sync-client)
    - [Manual acquire/release](#manual-acquirerelease)
    - [Parameters](#parameters)
  - [Multi-server sharding](#multi-server-sharding)
<!--toc:end-->

A lightweight distributed lock server using a simple line-based TCP protocol with FIFO ordering, automatic lease expiry, and background renewal.

[Read the docs here](https://mtingers.github.io/dflockd/)

## Quick start

```bash
# Install
uv sync

# Run the server
uv run dflockd
```

The server listens on `0.0.0.0:6388` by default.

## Server configuration

All tuning is via environment variables:

| Variable | Default | Description |
|---|---|---|
| `DFLOCKD_HOST` | `0.0.0.0` | Bind address |
| `DFLOCKD_PORT` | `6388` | Bind port |
| `DFLOCKD_DEFAULT_LEASE_TTL_S` | `33` | Default lock lease duration (seconds) |
| `DFLOCKD_LEASE_SWEEP_INTERVAL_S` | `1` | How often to check for expired leases |
| `DFLOCKD_GC_LOOP_SLEEP` | `5` | How often to prune idle lock state |
| `DFLOCKD_GC_MAX_UNUSED_TIME` | `60` | Seconds before idle lock state is pruned |
| `DFLOCKD_MAX_LOCKS` | `1024` | Maximum number of unique lock keys |
| `DFLOCKD_READ_TIMEOUT_S` | `23` | Client read timeout (seconds) |
| `DFLOCKD_AUTO_RELEASE_ON_DISCONNECT` | `1` | Release locks when a client disconnects (`1`, `yes`, `true` to enable) |

## CLI arguments

Settings can also be passed as command-line flags. Environment variables take precedence over CLI arguments.

```bash
uv run dflockd --port 7000 --max-locks 512
```

| Flag                     | Default   | Env var override                 |
| ------------------------ | --------- | -------------------------------- |
| `--host`                 | `0.0.0.0` | `DFLOCKD_HOST`                   |
| `--port`                 | `6388`    | `DFLOCKD_PORT`                   |
| `--default-lease-ttl`    | `33`      | `DFLOCKD_DEFAULT_LEASE_TTL_S`    |
| `--lease-sweep-interval` | `1`       | `DFLOCKD_LEASE_SWEEP_INTERVAL_S` |
| `--gc-interval`          | `5`       | `DFLOCKD_GC_LOOP_SLEEP`          |
| `--gc-max-idle`          | `60`      | `DFLOCKD_GC_MAX_UNUSED_TIME`     |
| `--max-locks`            | `1024`    | `DFLOCKD_MAX_LOCKS`              |
| `--read-timeout`         | `23`      | `DFLOCKD_READ_TIMEOUT_S`         |
| `--auto-release-on-disconnect` / `--no-auto-release-on-disconnect` | `true` | `DFLOCKD_AUTO_RELEASE_ON_DISCONNECT` |

## Protocol

The wire protocol is line-based UTF-8 over TCP. Each request is exactly 3 lines: `command\nkey\narg\n`.

### Commands

**Lock (acquire)**

```
l
<key>
<timeout_s> [<lease_ttl_s>]
```

Response: `ok <token> <lease_ttl>\n` or `timeout\n`

**Renew**

```
n
<key>
<token> [<lease_ttl_s>]
```

Response: `ok <seconds_remaining>\n` or `error\n`

**Release**

```
r
<key>
<token>
```

Response: `ok\n` or `error\n`

### Behavior

- Locks are granted in strict FIFO order per key.
- Leases expire automatically if not renewed. On expiry, the lock passes to the next waiter.
- Connections that disconnect have their held locks released automatically.

## Client usage

### Async client

```python
import asyncio
from dflockd.client import DistributedLock

async def main():
    async with DistributedLock("my-key", acquire_timeout_s=10) as lock:
        print(lock.token, lock.lease)
        # critical section — lease auto-renews in background

asyncio.run(main())
```

### Sync client

```python
from dflockd.sync_client import DistributedLock

with DistributedLock("my-key", acquire_timeout_s=10) as lock:
    print(lock.token, lock.lease)
    # critical section — lease auto-renews in background thread
```

### Manual acquire/release

Both clients support explicit `acquire()` / `release()` outside of a context manager:

```python
from dflockd.sync_client import DistributedLock

lock = DistributedLock("my-key")
if lock.acquire():
    try:
        pass  # critical section
    finally:
        lock.release()
```

### Parameters

| Parameter           | Default                 | Description                                                             |
| ------------------- | ----------------------- | ----------------------------------------------------------------------- |
| `key`               | _(required)_            | Lock name                                                               |
| `acquire_timeout_s` | `10`                    | Seconds to wait for lock acquisition                                    |
| `lease_ttl_s`       | `None` (server default) | Lease duration in seconds                                               |
| `servers`           | `[("127.0.0.1", 6388)]` | List of `(host, port)` tuples                                           |
| `sharding_strategy` | `stable_hash_shard`     | `Callable[[str, int], int]` — maps `(key, num_servers)` to server index |
| `renew_ratio`       | `0.5`                   | Renew at `lease * ratio` seconds                                        |

## Multi-server sharding

When running multiple dflockd instances, the client can distribute keys across servers using consistent hashing. Each key always routes to the same server.

```python
from dflockd.sync_client import DistributedLock

servers = [("server1", 6388), ("server2", 6388), ("server3", 6388)]

with DistributedLock("my-key", servers=servers) as lock:
    print(lock.token, lock.lease)
```

The default strategy uses `zlib.crc32` for stable, deterministic hashing. You can provide a custom strategy:

```python
from dflockd.sync_client import DistributedLock

def my_strategy(key: str, num_servers: int) -> int:
    """Route all keys to the first server."""
    return 0

with DistributedLock("my-key", servers=servers, sharding_strategy=my_strategy) as lock:
    pass
```
