You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello.
The documentation of the module does not describe in detail the interaction with the cluster.
Could you describe in more detail the process of raising a cluster on one machine on several ports at once?
and run it, a new configuration file appears in the system, directories too, but the service launched with config file /etc/redis/redis.conf . What's wrong? If i add custom service_name - puppet can't add it as new service. I am on Debian.
Is it able to manage redis nodes with a specific configuration file? Is it able to generate startup files for each node (/etc/init.d/redis_port)?
I tried to hide the configuration parameters in a hash to raise several nodes through the create_resources, but I did not succeed. Describe, please, the way with which you can, for example, to up 6 nodes on one server on different ports.
Thank you!
The text was updated successfully, but these errors were encountered:
Hello.
The documentation of the module does not describe in detail the interaction with the cluster.
Could you describe in more detail the process of raising a cluster on one machine on several ports at once?
When I specify something like:
and run it, a new configuration file appears in the system, directories too, but the service launched with config file /etc/redis/redis.conf . What's wrong? If i add custom service_name - puppet can't add it as new service. I am on Debian.
Is it able to manage redis nodes with a specific configuration file? Is it able to generate startup files for each node (/etc/init.d/redis_port)?
I tried to hide the configuration parameters in a hash to raise several nodes through the create_resources, but I did not succeed. Describe, please, the way with which you can, for example, to up 6 nodes on one server on different ports.
Thank you!
The text was updated successfully, but these errors were encountered: