Skip to content

EZP-25972: Clustering guide improvement #443

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Nov 13, 2018
Merged

Conversation

DominikaK
Copy link

Question Answer
JIRA Ticket https://jira.ez.no/browse/EZP-25972
Versions all

Reorganizes sections as suggested in ticket description.

This is a second attempt at #428, which got too many conflicts after #418

Memcached must not be bound to the local address if clusters are in use, or user logins will fail.
To avoid this, in `/etc/memcached.conf` take a look under `# Specify which IP address to listen on. The default is to listen on all IP addresses`
- [Solr](solr.md) for better search and performance
- a CDN for improved performance and faster ping time worldwide

This comment was marked as resolved.


> Listen on <addr>; default to INADDR\_ANY. <addr> may be specified as host:port. If you don't specify a port number, the value you specified with -p or -U is used. You may specify multiple addresses separated by comma or by using -l multiple times. This is an important option to consider as there is no other way to secure the installation. Binding to an internal or firewalled network interface is suggested.
See [Redis Cache Adapter in Symfony documentation](https://symfony.com/doc/3.4/components/cache/adapters/redis_adapter.html#configure-the-connection)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rather link to our doc (persistence cache), as we might introduce own adapters soon that improve performance.

Align this with the link done on memcached, so both initial section on Redis links to persistence cache doc, as well as the alternative section.


It is also recommended to use:
To use Redis, you need to set `cache_service_name` to `cache.redis`.
Copy link
Contributor

@andrerom andrerom Nov 6, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

skip, it will change, lets not duplicate please

At least it looks strange to have config for Redis here, but config for all others the other place.

The regular `php bin/console cache:clear` command does not clear Redis persistence cache.
To clear it, use a dedicated Symfony command: `php bin/console cache:pool:clear cache.redis`.

##### Redis Clustering
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can make sense to have here, but then we should rewrite it to more clearly cover both sessions and persistence cache topics. and link to it

@andrerom
Copy link
Contributor

andrerom commented Nov 6, 2018

@DominikaK I think I see what you are trying to do => write a guide to setting up a (specific) cluster setup.

Wouldn't it be better to continue letting this be general doc landing page for cluster where we document all possibilities, and write a separate guide / tutorial page where we guide how a specific setup is accomplished?

@DominikaK
Copy link
Author

@andrerom you're right, let's go it slowly and resolve this ticket first, then we can plan for extending the doc on clustering in future.

[Redis](http://redis.io/), an in-memory data structure store, is the recommended cache solution for clustering.
Redis is used via [Redis pecl extension](https://pecl.php.net/package/redis).

An alternative cache solution for cluster setups is [using Memcached](persistence_cache.md#memcached).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not needed here, memcached is explained further down and this is section dedicated to redis

@DominikaK DominikaK merged commit 2a6e37e into master Nov 13, 2018
DominikaK pushed a commit that referenced this pull request Nov 13, 2018
DominikaK pushed a commit that referenced this pull request Nov 13, 2018
@DominikaK DominikaK deleted the clustering-update-again branch November 13, 2018 07:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants