Re: Tomcat Clustering Roadmap And Max Node Limit
On 04/04/2025 02:42, Chuck Caldarale wrote: On 2025 Apr 3, at 19:57, Tim N wrote: For a long time up to the latest version 11 documentation, there has been a recommended maximum limit of 4 nodes per cluster. https://tomcat.apache.org/tomcat-11.0-doc/cluster-howto.html "This works great for smaller clusters, but we don't recommend it for larger clusters — more than 4 nodes or so." Are there any plans to improve this? It's a pity to have to change the architecture when going from, say, 3 notes to 8 by introducing farms. What is the next simplest free cluster to move to? Redis? Any idea how cluster farming compares with redis? What other options are there? I may be misreading the documentation, but I think the 4-node restriction applies to the DeltaManager, and using the BackupManager removes the limitation. Chuck is correct. The issue with the DeltaManager is that the cluster traffic scales with the square of the number of nodes. For the BackupManager traffic scales linearly with the number of nodes. The limit of 4 is one of those values that should work with most applications. Depending on your application, the actual limit may be higher. Mark - Chuck - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Using classes from forked packages
Dear Tomcat users and supporters, The Apache Tomcat software uses forks from packages as Apache Commons FileUpload and others. However, do you not recommend using classes from such Tomcat packages within a web app that only will run on Tomcat? (e.g. org.apache.tomcat.util.http.fileupload) In addition, must such forked packages not be contain all classes of the origin? Moreover, app developer might expect that Tomcat developers can delete unused classes. This might be stupid questions, but I came across an issue after updating Tomcat because of used forked classes and like to request for confirmation. Best regards and have a nice weekend, Alexander - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Using classes from forked packages
On 04/04/2025 18:18, Alexander Norz wrote: Dear Tomcat users and supporters, The Apache Tomcat software uses forks from packages as Apache Commons FileUpload and others. However, do you not recommend using classes from such Tomcat packages within a web app that only will run on Tomcat? (e.g. org.apache.tomcat.util.http.fileupload) Depending on any Tomcat internals is not recommended. See the "API Stability" section of the RELEASE-NOTES. In addition, must such forked packages not be contain all classes of the origin? Tomcat internals will use as little or as much as the Tomcat developers deem necessary from any forked package. Moreover, app developer might expect that Tomcat developers can delete unused classes. Yes. This might be stupid questions, but I came across an issue after updating Tomcat because of used forked classes and like to request for confirmation. They are good questions but I will note the answers are all in the "API Stability" section of the release notes. Mark Best regards and have a nice weekend, Alexander - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
