What are the drawbacks of session replication on Tomcat? -
I was trying to decide what is better in the Tommack + Apache reverse proxy mode for replication of the session. What is more common on deployment? Session replication or stick session? Are there any drawbacks for session replication?
Thanks
I can tell if you go for session replication Following considerations.
Display
The main drawback will be on display in repeated sessions, the cluster contains a copy of the session data on all servers
DeltaManager (Default) and backup manager
>
This URL
using the above configuration will use Delta Manager to repeat session delta All-to-all sessions will enable replication. From all-to-nothing we mean that all other nodes are repeated in the session cluster. It works great for small clusters, but we do not recommend it for large groups (many tomcat nodes) when using Delta Manager it will mimic all the nodes, even the nodes that are not deployed Are there.
To resolve this problem, you want to use the backup manager, this manager simply copies session data to a backup node, and not only for the nodes that the application has deployed . Negative side of BackupManager: Delta Manager is not as much a trial as
Read for good design tips for cluster if session replication is enabled.
Memory
How many concurrent users will kill the application? More users are accumulated in more data sessions, and therefore a surcharge for session replication.
Code Ideas
In addition to this you need to ensure the data is being serialized in the session by the application being serializable. To mimic the session state, there are some upper part of the serialing session data. Session size is a good idea to be small, so developers have to check the amount of data to be inserted in the session.
Sticky Sessions
Given these ideas, it really depends on the severity of the matters used. If you go for sticky sessions alone, there is an opportunity for user data loss during an important trip.
Do you mean to recover from it - like: Order or payment travel by maintaining important data in each stage? If the user does not have to login and resume it is fine for those websites which are not transactions, but browse the brochureware type of data or fill out the form to capture the data, which is not the payment etc.
Comments
Post a Comment