Overview's and notifications not pushed/updated via websocket

lorn · March 16, 2021, 12:52am

I now have a working solution

github.com/zammad/zammad

Add redis as an (optional) session store backend

zammad:develop ← djmaze:add-redis-session-store

opened 12:49AM - 16 Mar 21 UTC

djmaze

+610 -335

As [discussed on the community forum](https://community.zammad.org/t/overviews-a…nd-notifications-not-pushed-updated-via-websocket/5854), it is currently a bit of a struggle to make a Zammad work on a multi-machine cluster. The main problem is the use of a shared directory as a kind of message queue for the sessions. Sharing that directory via a distributed filesystem turns out to be really problematic. A much more suitable tool for this kind of work is Redis. I thus refactored the sessions module to allow for different store backends and implemented a Redis backend in addition to the file backend. In my local tests, this seems to work well. I still have to try this out in production though. I am a bit unsure with the naming (is `store` the right term to use for the backends?). Also, I did not yet have a look at the tests in order to see if or how the new backend can be tested. In order to use this, you need to set the env variable `REDIS_URL` to a running Redis server for the Zammad services. Let me know what you think of this.

olafbuitelaar · March 16, 2021, 9:37am

uhmm…it looks like here are some session files are written out too; zammad/node.rb at 9922f5b54fab5820b6043063a999f83574530755 · zammad/zammad · GitHub

lorn · March 16, 2021, 9:27pm

Ah, good catch! That seems to be used only when multiple session workers are activated, but of course should be ported as well.

lorn · March 16, 2021, 10:59pm

I converted that as well.

olafbuitelaar · April 23, 2021, 5:30pm

not directly related to this, but it would be interesting to know what role tmp/cache_file_store_production play’s in the whole shared storage.

system · August 21, 2021, 5:31pm

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.