View Attach Info

Add new attachment

Only authorized users are allowed to upload new attachments.

This page (revision-7) was last changed on 05-Dec-2023 05:32 by Ben Spink

This page was created on 05-Dec-2023 05:32 by Ben Spink

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 1 changed one line
Session replication only functions for [Enterprise Licenses|Enterprise License Enhancements]. The servers participating in the replication must have a manual setting configuration done in their prefs.xml file.
Session replication only functions for [Enterprise Licenses|Enterprise License Enhancements]. The servers participating in the replication must have a manual setting configuration done in their prefs.xml file. The port specified must be open between machines as this will be used for the replication messages.
At line 5 changed 2 lines
Example for the first machine:
Example for the first machine:\\
At line 11 changed 2 lines
and on the second machine a reference back to the first machine.
and on the second machine a reference back to the first machine:\\
At line 17 changed one line
To enable user replication from changes made in the user manager, edit the prefs.xml file and set this flag to true.
In the case of multiple machines, each machine references the other machines with a comma separated list. DNS names are also OK here as well:\\
{{
<replicate_session_host_port>machine1:7800,machine3:7800</replicate_session_host_port>
}}
At line 20 added 2 lines
To enable user replication from changes made in the user manager, edit the prefs.xml file and set this flag to true.\\
At line 23 changed 2 lines
In some special cases you may want the other functionality without the overhead of all session information being replicated between machines. In this case a user would have to re-login if they were suddenly redirected to the other machine...but it avoid wasted resources from replicating all details about a user between machines. Set this to false.
In some special cases you may want the other functionality without the overhead of all session information being replicated between machines. In this case a user would have to re-login if they were suddenly redirected to the other machine...but it avoid wasted resources from replicating all details about a user between machines. Set this to false.\\
At line 30 added 10 lines
If you're using the "S3Crush" mode for users, there is a flag to replicate this config between servers too.\\
{{
<s3crush_replicated>true</s3crush_replicated>
}}
Job configurations can be replicated too:\\
{{
<replicate_jobs>true</replicate_jobs>
}}
Version Date Modified Size Author Changes ... Change note
7 05-Dec-2023 05:32 1.805 kB Ben Spink to previous
6 05-Dec-2023 05:32 1.801 kB Ben Spink to previous | to last
5 05-Dec-2023 05:32 1.7 kB Ben Spink to previous | to last
4 05-Dec-2023 05:32 1.184 kB Ben Spink to previous | to last
3 05-Dec-2023 05:32 0.769 kB Ben Spink to previous | to last
2 05-Dec-2023 05:32 0.58 kB Ben Spink to previous | to last
1 05-Dec-2023 05:32 1.393 kB Ben Spink to last
« This page (revision-7) was last changed on 05-Dec-2023 05:32 by Ben Spink
G’day (anonymous guest)
CrushFTP11 | What's New

Referenced by
...nobody

JSPWiki