Repository navigation
IoT Agent memory and tutorial clean-up: one agent worker, no retried creates, services stop removes only the tutorial's - #19
Merged
jason-fox merged 1 commit intoNov 5, 2026
Conversation
…creates, services stop removes only the tutorial's - IoT Agent: `IOTA_MULTI_CORE=false`. With `true` the agent forks one worker per *host* CPU core, although the container is limited to 2 CPUs and 1 GiB. On a 32-core machine an idle agent already uses 972 MiB and is killed for running out of memory (83 MiB with `false`). A provisioning request then gets an empty reply and the `services` start fails. - No retry on the device and service-group POSTs. `--retry-all-errors` repeats a create that has already reached the IoT Agent. Every retry is then a 409, and a batch that was only partly created is never completed. `services` already waits for the agent to be healthy before these requests. - `services stop` removes only the tutorial's containers, volumes and networks. It removed *every* container on the machine (`docker rm -f $(docker ps -aq)`) and every unused volume (`docker volume ls -qf dangling=true`), the user's own included. Now: the containers labelled `org.fiware=tutorial`, with their anonymous volumes (`rm -v`); the unused volumes of the `fiware` compose project; the tutorial's networks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
IOTA_MULTI_CORE=false. Withtruethe agent forks one worker per host CPU core, although the container is limited to 2 CPUs and 1 GiB. On a 32-core machine an idle agent already uses 972 MiB and is killed for running out of memory (83 MiB withfalse). A provisioning request then gets an empty reply and theservicesstart fails.--retry-all-errorsrepeats a create that has already reached the IoT Agent. Every retry is then a 409, and a batch that was only partly created is never completed.servicesalready waits for the agent to be healthy before these requests.services stopremoves only the tutorial's containers, volumes and networks. It removed every container on the machine (docker rm -f $(docker ps -aq)) and every unused volume (docker volume ls -qf dangling=true), the user's own included. Now: the containers labelledorg.fiware=tutorial, with their anonymous volumes (rm -v); the unused volumes of thefiwarecompose project; the tutorial's networks.Tested with the coraine stack: Concise-Format, Context-Providers, Short-Term-History, Time-Series-Data, IoT-Agent and IoT-Agent-JSON start and run their README steps with these changes. After six starts and stops, a container started outside the tutorials is still running and no tutorial volume is left.
stoppingContainersis now the same function in all sixteen NGSI-LD tutorials.🤖 Generated with Claude Code