Search results
Create the page "Cluster" on this wiki! See also the search results found.
- ...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki> ...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki>347 KB (47,794 words) - 13:34, 31 January 2017
- ...cluster, the different user should be connected to different nodes of the cluster2 KB (285 words) - 12:27, 30 April 2015
- ...most cases, you want to use the same configuration throughout the whole ox cluster, so you should make sure to use the same ''filestore-sproxyd.properties'' c * Open a terminal on a running backend server of your OX cluster5 KB (655 words) - 10:35, 5 May 2015
- ...most cases, you want to use the same configuration throughout the whole ox cluster, so you should make sure to use the same ''filestore-s3.properties'' config * Open a terminal on a running backend server of your OX cluster7 KB (1,021 words) - 08:03, 9 June 2021
- ...setup a single Guard instance on an existing Open-Xchange installation, no cluster ...should include the URL suffix <code>/guardadmin</code>. In the event of a cluster setup, any Guard server can be referenced here, as it is not session specif44 KB (6,324 words) - 12:12, 9 October 2023
- | <nowiki>Defines the name of the Cassandra cluster. Technically this name does not correlate with the name configured in the real Cassandra cluster, but it's rather used to distinguish366 KB (50,420 words) - 07:11, 29 September 2017
- ...done and the lock will be released. This happens with each node within the cluster.6 KB (785 words) - 10:03, 14 March 2019
- ...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki> ...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki>293 KB (39,973 words) - 13:36, 1 July 2015
- ...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki> ...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki>321 KB (44,146 words) - 07:59, 2 December 2015
- ...open-xchange/etc-templates/documents/mode-server-combined/nature-ce-server/cluster-node.xml'''''to create those file. <cluster>23 KB (2,471 words) - 10:59, 2 October 2015
- ...ne OX server fail, this is transparently handled by others within the same cluster. ...n-xchange/etc-templates/documents/mode-server-distributed/nature-ce-server/cluster-node.xml'''''to create those file.32 KB (3,487 words) - 15:29, 12 January 2016
- * [[AppSuite:Running_a_cluster| Configuration Cluster-Setup]]7 KB (809 words) - 08:19, 29 July 2019
- ...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki> ...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki>301 KB (41,323 words) - 19:56, 2 December 2015
- ...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki> ...nce each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </nowiki>333 KB (45,761 words) - 15:55, 17 May 2016
- * [[AppSuite:Running_a_cluster| Configuration Cluster-Setup]]7 KB (837 words) - 08:19, 29 July 2019
- * Disable Hazelcast cluster discovery22 KB (3,197 words) - 07:16, 4 April 2016
- ...setup a single Guard instance on an existing Open-Xchange installation, no cluster ...uard server should include the url suffix /guardadmin . In the event of a cluster setup, any Guard server can be referenced here, as it is not session specif38 KB (5,758 words) - 18:25, 13 April 2017
- Abuse Shield runs on a cluster of servers, and integrates with authenication systems to detect abuse, brut ...red architecture – Login reports are shared between all the servers in a cluster so there is a single view of abuse31 KB (4,248 words) - 12:18, 9 June 2022
- # Alternatively select one or more hosts of your cluster to be restricted to handle only eas/usm requests19 KB (2,677 words) - 08:32, 8 December 2022
- ...masters. However if you use only one (active) Maxscale instance per target cluster at a time (maybe with some active-passive HA setup), it might be beneficial5 KB (750 words) - 12:16, 18 October 2017
- ...setup a single Guard instance on an existing Open-Xchange installation, no cluster ...should include the URL suffix <code>/guardadmin</code>. In the event of a cluster setup, any Guard server can be referenced here, as it is not session specif39 KB (5,606 words) - 09:59, 5 February 2020