Latest release: 3.0.4, released 16 February 2026.
Goals
- Improve propagation.
- Improve log readability.
- Improve storage management.
- Provide more control to the operators.
Upgrade
The upgrade does not require any changes in configuration when upgrading from 1.1.*.
This release was tested on the preview tag first and is now on the latest tag.
The image path should be set to the following:
public.ecr.aws/cornucopias/nodes/pool-server:latestOnce it is time to upgrade, the following command will pull an updated image and restart the pool server using the new image.
docker compose pull
docker compose up -dThe version of the pool server can be verified by looking at the first few lines of the log output.
[2026-04-01T14:57:01Z INFO filenodes_pool_server] Pool Server Version: 3.0.4
Changes
- Propagation now runs slow and steady. The pool server downloads a small group of chunks, activates them (making them available to others), and repeats until all of the chunks are downloaded.
- Registrations are no longer skipped during a long download.
- The log output should be run at the info level which is the default log level. The logs should provide a clear story of what is happening. Errors should be understandable. Actions should be clear. Timings should be available.
- An existing environment variable should be understood.
FILENODES_POOL_MAX_CACHE_SIZEis a variable that should be set to the max available storage. The default is 100G. The intent is that the pool will never exceed this storage amount. More or less storage is ok because we will use what you give us. The new normal is that we will keep this as full as possible. - A new environment variable
FILENODES_POOL_CONCURRENT_DOWNLOADSwill determine how fast you download the cache. This is not a race, so please do not go crazy with this one. For the sake of slow and steady, defaulting to1should be adequate for 99% of pools. - The last documented environment variable is
FILENODES_POOL_DOWNLOAD_BATCH_SIZEwhich will determine how many chunks to download before activating and making them available to other pool servers to download. - Before doing any work, the pool server must know where it is, so it does requests to all of the system pools to measure latencies. We have reduced the number of latency requests per system pool from 5 to 3. This will make the check a little quicker.
- Fixed a bug that when a system pool is down, the pool server will choose the region of the system pool that was down.
Sample Configurations
Note: No changes are necessary for the upgrade. These are just examples on how one may want to update their configurations for modified behavior.
Default
services:
pool-server:
image: public.ecr.aws/cornucopias/nodes/pool-server:latest
ports:
- "8001:8001"
restart: unless-stopped
environment:
FILENODES_POOL_ACCESS_KEY: "PASTE ACCESS KEY HERE"
FILENODES_POOL_PUBLIC_PORT: "8001"
FILENODES_POOL_MAX_CACHE_SIZE: "100"
FILENODES_POOL_CONCURRENT_DOWNLOADS: "1"
volumes:
- D:\CornPoolServer\Cache:/cacheLots of Storage
services:
pool-server:
image: public.ecr.aws/cornucopias/nodes/pool-server:latest
ports:
- "8001:8001"
restart: unless-stopped
environment:
FILENODES_POOL_ACCESS_KEY: "PASTE ACCESS KEY HERE"
FILENODES_POOL_PUBLIC_PORT: "8001"
FILENODES_POOL_MAX_CACHE_SIZE: "1000"
FILENODES_POOL_CONCURRENT_DOWNLOADS: "2"
volumes:
- D:\CornPoolServer\Cache:/cacheChange Log
3.0.2
- Failure retry delay for
get_cache_files()increased from fixed 60 seconds to a random jitter between 10-20 minutes to avoid thundering herd on API timeouts. - Registration log now shows duration until expiration in minutes and seconds (e.g. "58m 47s") to help confirm jitter in registration TTLs.
3.0.3
- JWKS verifying keys are now refreshed every registration cycle instead of once at startup, so key rotations take effect without restarting the pool servers.
3.0.4
- Pass source pool's registration ID (instead of client's own) to the downloader, fixing misleading "from registration" log messages and enabling correct skip-tracking of unreachable source pools.
Upgrade Expectations
All pool servers were expected to be on 3.0.* by June 1, 2026. If yours is still on an older version, upgrade it now.