v3.0.1

version 3 0 1 goals improve propagation improve log readability improved storage management provide more control to the operators upgrade if you would like to upgrade your pool server before the latest tag is updated, you will need to change your image tag to preview public ecr aws/cornucopias/nodes/pool server\ preview if you want to wait for a bit more testing, that is ok we will move the new server to the latest tag soon and let you all know when we do once it is time to upgrade, the following command will pull an updated image docker compose pull docker compose up d changes the propagation is now running slow and steady pool server will pull download small groupings of chunks then activate them (making them available to others) this will loop until all of the chunks are downloaded registrations will not be skipped when downloading a long time 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 fixable actions should be clear timings should be available an existing environmental variable should be understood filenodes pool max cache size is 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 environmental variable filenodes pool concurrent downloads will determine how fast you download the cache this is not a race, so i would not go crazy with this one for the sake of slow and steady, we are defaulting to 1 download at a time the last documented environmental variable is filenodes pool download batch size which 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 much 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 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" rust log "info" volumes \ d \cornpoolserver\cache /cache lots 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" rust log "info" volumes \ d \cornpoolserver\cache /cache