Search results
Create the page "Cluster" on this wiki! See also the search results found.
- ...ed in [https://oxpedia.org/wiki/index.php?title=AppSuite:Running_a_cluster Cluster Setup]. |MariaDB Server, Galera Cluster13 KB (1,753 words) - 17:04, 6 May 2024
- * [[AppSuite:Running_a_cluster| Configuration Cluster-Setup]]6 KB (709 words) - 08:17, 29 July 2019
- * [[AppSuite:Running_a_cluster| Configuration Cluster-Setup]]6 KB (707 words) - 08:16, 29 July 2019
- | com.openexchange.cluster.name | <nowiki>Specifies the name of the cluster. Each node in the cluster should be configured with the same name. Required. </nowiki>231 KB (31,767 words) - 10:27, 19 April 2013
- =Cluster setup= [[File:GrizzlOXClusterSetup.png|left|alt=The default cluster setup.]]21 KB (3,032 words) - 06:05, 18 September 2019
- ...t to protect against login/authentication abuse. OX Abuse Shield runs on a cluster of servers, and integrates with both OX App Suite and Dovecot to detect abu == Cluster-Setup ==9 KB (1,287 words) - 16:02, 28 November 2023
- * [[AppSuite:Running_a_cluster| Configuration Cluster-Setup]]5 KB (633 words) - 09:14, 3 April 2019
- ...tasked with designing and maintaining the configuration of an OX server or cluster, information contained in this document will acquaint you with options in O9 KB (1,339 words) - 14:52, 3 April 2019
- <div class="title">How to move database schemas from one database cluster to another</div> ...e cluster (hazelcast grid) operate on the same databases, one node of each cluster must be reachable via RMI. Of course all groupware nodes of the whole deplo9 KB (1,098 words) - 14:29, 23 April 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>300 KB (41,181 words) - 07:10, 9 July 2015
- Failed to distribute permanent listeners among cluster nodes23 KB (3,269 words) - 10:15, 20 September 2018
- ...''. Turn the node off, update, turn it on again, make sure it works in the cluster. Have a look here, too: [[Running_a_cluster#Upgrading_a_single_Node|Upgradi * If you don't have a cluster of OX nodes, then your complete installation needs to be taken down tempora15 KB (2,156 words) - 12:09, 9 October 2023
- <div class="title">Running a cluster</div> ...X-communication over the network, multiple Open-Xchange servers can form a cluster. This brings different advantages regarding distribution and caching of vol58 KB (8,939 words) - 14:04, 30 January 2020
- If OX Documents functionality is used for guest users in a cluster of application servers, this setting needs to be adjusted to <code>false</c54 KB (8,627 words) - 13:37, 7 December 2018
- ...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>271 KB (37,062 words) - 13:43, 1 July 2015
- * [[AppSuite:Running_a_cluster| Configuration Cluster-Setup]]4 KB (477 words) - 08:17, 29 July 2019
- * [[AppSuite:Running_a_cluster| Configuration Cluster-Setup]]5 KB (559 words) - 08:17, 29 July 2019
- * [[AppSuite:Running_a_cluster| Configuration Cluster-Setup]]5 KB (625 words) - 08:17, 29 July 2019
- | com.openexchange.cluster.name | <nowiki>Specifies the name of the cluster. Each node in the cluster should be configured with the same name. Required. </nowiki>231 KB (31,760 words) - 11:29, 16 April 2013
- | com.openexchange.cluster.name | <nowiki>Specifies the name of the cluster. Each node in the cluster should be configured with the same name. Required. </nowiki>247 KB (33,845 words) - 11:37, 16 August 2013
- ...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>268 KB (37,155 words) - 12:16, 21 October 2015
- ...r tracing every single login request passed between different systems in a cluster. The value should be some token that is unique for every login request. Thi138 KB (17,726 words) - 05:31, 20 October 2017
- * [[AppSuite:Running_a_cluster| Configuration Cluster-Setup]]6 KB (668 words) - 08:18, 29 July 2019
- ...ase that the web server is on a dedicated system or maybe even has its own cluster. The default package is installed on the OX application server, and the sec11 KB (1,757 words) - 10:01, 22 May 2017
- When multiple Open-Xchange Servers are configured within a cluster Session and Loadbalancing needs to be set up.5 KB (778 words) - 08:33, 8 February 2018
- ...is sufficient to take over the IP address on the other MySQL server in the cluster to stay fully in operation. ...SQL database and to '''read''' from the '''second''' MySQL database in one cluster. This will distribute the load during normal operation as smooth as possibl5 KB (809 words) - 08:33, 8 February 2018
- # Since each received feedback is processed cluster-wide, only one node in the # cluster should be enabled here.22 KB (3,224 words) - 13:19, 18 December 2023
- ...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>351 KB (48,276 words) - 15:48, 31 January 2017
- ...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>280 KB (38,131 words) - 21:26, 5 March 2014
- * [[AppSuite:Running_a_cluster| Configuration Cluster-Setup]]6 KB (697 words) - 08:18, 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>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