Issue with caching

[danlong]

I'm currently experiencing an issue where I create a new category/subcategory and it doesn't show for all users (with privileges set to allow everyone to view/read).

I'm running NodeBB on two server instances (on Azure). It seems that the server which is used to create the new category shows on the frontend. The other server instance, however, doesn't show the new category.

I've checked the category API, in the server that was used to create the category it appears in the JSON, but it doesn't appear in the API on the other server instance.

The two servers only share 1 database, so the category data must be there. How long does it take for the cache to refresh?

[baris]

The cache stays as long as it is not full and it is not invalidated. Sounds like you need to setup pubsub so changes you make on one server are propagated to the others.

[julian]

@danlong Please consult this section of the documentation for more info re: pubsub: https://docs.nodebb.org/configuring/scaling/#configure-redis

[danlong]

Thank-you @baris and @julian for your response

I've added a flag in my config.json isCluster: true
Is that enough to make the pubsub work with postgres or do I need to add an additional redis server and the config block?

[baris]

That should be enough I think. You can also add singleHostCluster: true If all your nodebb processes are on a single server.

[danlong]

Thank you both, this resolved the issue