I've attempted to split the API and microservices services using the split workers technique found in the Jobs and Workers section on the docs. Immich is now showing that there are no jobs waiting or to be completed, and it occurs to me that the containers don't really have any way to communicate: They can talk to over the internal Docker Compose network, but they don't know the other's IP address or hostname. Are they able to communicate at all?
#When splitting API and microservices workers, do they communicate with each other?
1 messages · Page 1 of 1 (latest)
:wave: Hey @prime compass,
Thanks for reaching out to us. Please follow the recommended actions below; this will help us be more effective in our support effort and leave more time for building Immich
.
References
- Container Logs:
docker compose logsdocs - Container Status:
docker compose psdocs - Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
Checklist
- :ballot_box_with_check: I have verified I'm on the latest release(note that mobile app releases may take some time).
- :ballot_box_with_check: I have read applicable release notes.
- :blue_square: I have reviewed the FAQs for known issues.
- :blue_square: I have reviewed Github for known issues.
- :blue_square: I have tried accessing Immich via local ip (without a custom reverse proxy).
- :blue_square: I have uploaded the relevant logs, docker compose, and .env files using the buttons below or the
/uploadcommand. - :blue_square: I have tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
If this ticket can be closed you can use the /close command, and re-open it later if needed.
@prime compass uploaded
They communicate via redis & postgres
Ah, I see
It doesn't seem to be working, which is why I asked.
I tried to upload my logs but it's restricted to 4000 characters and the logs are around 30k
What part isn't working?
There are no jobs waiting, but there were hundreds before I upgraded.
I thought it might be to do with my external library, so I tried deleting it (I want to start again with it anyway) but nothing happened after it asked me "Are you sure?" and I said "Yes"
I found a similar issue on GitHub, but it still feels like it could be a me problem.
If you restart/recreate redis then the jobs will get wiped, that's normal
You can just click missing to start them up again