Re: backupManager - backup on all nodes and slowly
Yes no session is lost, and memory isn't wasted as with delta manager. With 4 nodes, when I ask 18080 or 28080 or 38080 node 48080 takes 2 more times than other two backup nodes, now I stop all now I tried starting nodes in order 2(8080),3,4,1 and started asking from 2 and not 4 was taking greater load but last started 1 (stil 2 times more than others) it looks like the last started tomcat takes greater load now I stop all now started in order 3,4,2, 1 was not started, asked 4, node 2 has two times more sessions than node 3. now I start node 1, ask 4, and now node 1 takes two time more than other backup nodes. now I added another fifth node 58080, started it, and now it takes 40% of backup sessions, and each of other 3 backup nodes takes 20% of backup session. Configuration is the same for all tomcats except from catalina.properties with port numbers. /node1$ ls conf logs run.sh temp work node 2, 3, and 4 are copy of node 1, nodes are started with ./run.sh with the same JVM parameters: node1$ cat run.sh export CATALINA_HOME=/szkolenie/tomcat export CATALINA_BASE=$(pwd) /szkolenie/tomcat/bin/catalina.sh run in server.xml: BR, Jakub On Tue, Feb 4, 2014 at 12:08 PM, Neven Cvetkovic wrote: > On Tue, Feb 4, 2014 at 4:08 AM, Ja kub wrote: > > > in Manager app I see: > > after > > ab -k -n 100 -p post.txt http://localhost:18080/petclinic/session/fill > > > > on 18080 in petclinic 100 sessions > > on 28080 in petclinic 25 sessions > > on 38080 in petclinic 25 sessions > > on 48080 in petclinic 50 sessions yes two times more > > > > after adding > > ab -k -n 900 -p post.txt http://localhost:18080/petclinic/session/fill > > > > on 18080 in petclinic 1000 sessions > > on 28080 in petclinic 250 sessions > > on 38080 in petclinic 250 sessions > > on 48080 in petclinic 500 sessions yes still two times more > > > > Is it not strange ? > > 18080, 28080, 38080, 48080 have the same configuration. > > > > What can be the cause ? > > > > > > > Jakub, > > Well, good thing is that all 100 sessions (+900 later) were > replicated/backed up (by the BackupManager) to other cluster members that > host the same application --> 25+25+50 = 100 and 250+250+500 = 1000. > > What happens if you repeat the experiment, but without one of the servers, > e.g. 28080? > > Can you send your full cluster configuration? How are you starting you > servers? Do they start with the same JVM parameters (-Xmx and -Xms)? > > Cheers! > n. >
Re: backupManager - backup on all nodes and slowly
On Tue, Feb 4, 2014 at 4:08 AM, Ja kub wrote: > in Manager app I see: > after > ab -k -n 100 -p post.txt http://localhost:18080/petclinic/session/fill > > on 18080 in petclinic 100 sessions > on 28080 in petclinic 25 sessions > on 38080 in petclinic 25 sessions > on 48080 in petclinic 50 sessions yes two times more > > after adding > ab -k -n 900 -p post.txt http://localhost:18080/petclinic/session/fill > > on 18080 in petclinic 1000 sessions > on 28080 in petclinic 250 sessions > on 38080 in petclinic 250 sessions > on 48080 in petclinic 500 sessions yes still two times more > > Is it not strange ? > 18080, 28080, 38080, 48080 have the same configuration. > > What can be the cause ? > > > Jakub, Well, good thing is that all 100 sessions (+900 later) were replicated/backed up (by the BackupManager) to other cluster members that host the same application --> 25+25+50 = 100 and 250+250+500 = 1000. What happens if you repeat the experiment, but without one of the servers, e.g. 28080? Can you send your full cluster configuration? How are you starting you servers? Do they start with the same JVM parameters (-Xmx and -Xms)? Cheers! n.
Re: backupManager - backup on all nodes and slowly
in Manager app I see: after ab -k -n 100 -p post.txt http://localhost:18080/petclinic/session/fill on 18080 in petclinic 100 sessions on 28080 in petclinic 25 sessions on 38080 in petclinic 25 sessions on 48080 in petclinic 50 sessions yes two times more after adding ab -k -n 900 -p post.txt http://localhost:18080/petclinic/session/fill on 18080 in petclinic 1000 sessions on 28080 in petclinic 250 sessions on 38080 in petclinic 250 sessions on 48080 in petclinic 500 sessions yes still two times more Is it not strange ? 18080, 28080, 38080, 48080 have the same configuration. What can be the cause ? On Mon, Feb 3, 2014 at 1:46 PM, Mark Thomas wrote: > On 03/02/2014 11:59, Ja kub wrote: > > Ok, thx, > > > > 2 questions: > > > > 1) If I will have only one very large session (about 100Mb), will memory > > increase only on one backup node, and on 2 other nodes in cluster memory > > will not increase ? > > You should see an increase on the primary and the backup node for that > session. The proxy sessions on the other two nodes should be minimal > since they just hold the session ID and the locations of the primary and > backup copies. > > > 2) On 18080 node, on which all queries where asked memory increased not > too > > much than 100Mb, and on each of other nodes memory also increased about > 100 > > Mb. > > Is it not strange ? I would expect about 35-50 Mb of memory increase on > > each of 3 backup nodes. Now memory consumption is the same as with Delta > > Manager. > > It depends a lot on what that memory is doing. You'd need to look very > carefully with a profiler to be sure of what was going on. > > You can use the Manager app to see which sessions are on which nodes in > what state. > > Mark > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Re: backupManager - backup on all nodes and slowly
On 03/02/2014 11:59, Ja kub wrote: > Ok, thx, > > 2 questions: > > 1) If I will have only one very large session (about 100Mb), will memory > increase only on one backup node, and on 2 other nodes in cluster memory > will not increase ? You should see an increase on the primary and the backup node for that session. The proxy sessions on the other two nodes should be minimal since they just hold the session ID and the locations of the primary and backup copies. > 2) On 18080 node, on which all queries where asked memory increased not too > much than 100Mb, and on each of other nodes memory also increased about 100 > Mb. > Is it not strange ? I would expect about 35-50 Mb of memory increase on > each of 3 backup nodes. Now memory consumption is the same as with Delta > Manager. It depends a lot on what that memory is doing. You'd need to look very carefully with a profiler to be sure of what was going on. You can use the Manager app to see which sessions are on which nodes in what state. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: backupManager - backup on all nodes and slowly
Ok, thx, 2 questions: 1) If I will have only one very large session (about 100Mb), will memory increase only on one backup node, and on 2 other nodes in cluster memory will not increase ? 2) On 18080 node, on which all queries where asked memory increased not too much than 100Mb, and on each of other nodes memory also increased about 100 Mb. Is it not strange ? I would expect about 35-50 Mb of memory increase on each of 3 backup nodes. Now memory consumption is the same as with Delta Manager. On Mon, Feb 3, 2014 at 12:36 PM, Mark Thomas wrote: > On 03/02/2014 11:31, Ja kub wrote: > > But time is not such a great problem for me. Time of execution was > > mentioned only "in addition" - there are 100 k requests. > > > > I am mainly interested in memory, and how BackupManager works. > > I hoped, that with BackupManager memory will increase on node which is > > queried and ONLY on one backup node, > > but here it is increasing on all 4 nodes in cluster. > > Should BackupManager be working as I write above, or do I understand it > > wrong ? > > Your understanding of the backup manager is not correct. > > See > > http://people.apache.org/~markt/presentations/2013-02-Apache-Tomcat-Clustering.pdf > > Mark > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Re: backupManager - backup on all nodes and slowly
On 03/02/2014 11:31, Ja kub wrote: > But time is not such a great problem for me. Time of execution was > mentioned only "in addition" - there are 100 k requests. > > I am mainly interested in memory, and how BackupManager works. > I hoped, that with BackupManager memory will increase on node which is > queried and ONLY on one backup node, > but here it is increasing on all 4 nodes in cluster. > Should BackupManager be working as I write above, or do I understand it > wrong ? Your understanding of the backup manager is not correct. See http://people.apache.org/~markt/presentations/2013-02-Apache-Tomcat-Clustering.pdf Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: backupManager - backup on all nodes and slowly
But time is not such a great problem for me. Time of execution was mentioned only "in addition" - there are 100 k requests. I am mainly interested in memory, and how BackupManager works. I hoped, that with BackupManager memory will increase on node which is queried and ONLY on one backup node, but here it is increasing on all 4 nodes in cluster. Should BackupManager be working as I write above, or do I understand it wrong ? On Mon, Feb 3, 2014 at 12:13 PM, Mark Thomas wrote: > On 03/02/2014 11:03, Ja kub wrote: > > Good question, sorry I didn't tell earlier, > > > > its tomcat 7.0.50 on linux, zip or tgz from download page, not from rpm. > > OK. Good to know it is the current release. > > It is probably time to fire up a profiler and see where all the time is > being spent. > > Mark > > > > On Mon, Feb 3, 2014 at 11:17 AM, Mark Thomas wrote: > > > >> On 03/02/2014 08:33, Ja kub wrote: > >>> I have configured no loadbalancer, > >>> > >>> I accessed tomcat directly > >> > >> Both things that it would have been useful to mention in your original > >> question. > >> > >> Before we go any further, how about telling us which Tomcat version you > >> are using? > >> > >> Mark > >> > >> > >>> tomcats are on 18080, 28080, 38080, 48080, > >>> In browser I used only 18080, this is my laptop test env, nobody else > >>> access it, > >>> 28080, 38080, 48080, where untouched by broser, but in jvisualvm their > >>> memory has increased by the same amount (about 100MB), it was increase > >>> after gc . > >>> > >>> Thx, > >>> Jakub > >> > >> > >> - > >> 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 > >
Re: backupManager - backup on all nodes and slowly
On 03/02/2014 11:03, Ja kub wrote: > Good question, sorry I didn't tell earlier, > > its tomcat 7.0.50 on linux, zip or tgz from download page, not from rpm. OK. Good to know it is the current release. It is probably time to fire up a profiler and see where all the time is being spent. Mark > On Mon, Feb 3, 2014 at 11:17 AM, Mark Thomas wrote: > >> On 03/02/2014 08:33, Ja kub wrote: >>> I have configured no loadbalancer, >>> >>> I accessed tomcat directly >> >> Both things that it would have been useful to mention in your original >> question. >> >> Before we go any further, how about telling us which Tomcat version you >> are using? >> >> Mark >> >> >>> tomcats are on 18080, 28080, 38080, 48080, >>> In browser I used only 18080, this is my laptop test env, nobody else >>> access it, >>> 28080, 38080, 48080, where untouched by broser, but in jvisualvm their >>> memory has increased by the same amount (about 100MB), it was increase >>> after gc . >>> >>> Thx, >>> Jakub >> >> >> - >> 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
Re: backupManager - backup on all nodes and slowly
Good question, sorry I didn't tell earlier, its tomcat 7.0.50 on linux, zip or tgz from download page, not from rpm. On Mon, Feb 3, 2014 at 11:17 AM, Mark Thomas wrote: > On 03/02/2014 08:33, Ja kub wrote: > > I have configured no loadbalancer, > > > > I accessed tomcat directly > > Both things that it would have been useful to mention in your original > question. > > Before we go any further, how about telling us which Tomcat version you > are using? > > Mark > > > > tomcats are on 18080, 28080, 38080, 48080, > > In browser I used only 18080, this is my laptop test env, nobody else > > access it, > > 28080, 38080, 48080, where untouched by broser, but in jvisualvm their > > memory has increased by the same amount (about 100MB), it was increase > > after gc . > > > > Thx, > > Jakub > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Re: backupManager - backup on all nodes and slowly
On 03/02/2014 08:33, Ja kub wrote: > I have configured no loadbalancer, > > I accessed tomcat directly Both things that it would have been useful to mention in your original question. Before we go any further, how about telling us which Tomcat version you are using? Mark > tomcats are on 18080, 28080, 38080, 48080, > In browser I used only 18080, this is my laptop test env, nobody else > access it, > 28080, 38080, 48080, where untouched by broser, but in jvisualvm their > memory has increased by the same amount (about 100MB), it was increase > after gc . > > Thx, > Jakub - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: backupManager - backup on all nodes and slowly
I have configured no loadbalancer, I accessed tomcat directly tomcats are on 18080, 28080, 38080, 48080, In browser I used only 18080, this is my laptop test env, nobody else access it, 28080, 38080, 48080, where untouched by broser, but in jvisualvm their memory has increased by the same amount (about 100MB), it was increase after gc . Thx, Jakub On Mon, Feb 3, 2014 at 9:04 AM, Mark Thomas wrote: > On 02/02/2014 22:59, Ja kub wrote: > > With below BackupManager backup manager configuration in server.xml > > heap memory increases over 100MB on each of four nodes in cluster. > > > > In addition time of > > ab -c 10 -n 10 -p post.txt > http://localhost:18080/petclinic/session/fill > > is about 150 seconds > > with default DeltaManager it is about 15 seconds. > > > > > channelSendOptions="6"> > > > >> className="org.apache.catalina.ha.session.BackupManager" > >expireSessionsOnShutdown="false" > >notifyListenersOnReplication="true" > >mapSendOptions="6"/> > > > > > > > > > > What may I be doing wrong ? > > Are you using sticky sessions on your load balancer? > > Mark > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
Re: backupManager - backup on all nodes and slowly
On 02/02/2014 22:59, Ja kub wrote: > With below BackupManager backup manager configuration in server.xml > heap memory increases over 100MB on each of four nodes in cluster. > > In addition time of > ab -c 10 -n 10 -p post.txt http://localhost:18080/petclinic/session/fill > is about 150 seconds > with default DeltaManager it is about 15 seconds. > > channelSendOptions="6"> > >className="org.apache.catalina.ha.session.BackupManager" >expireSessionsOnShutdown="false" >notifyListenersOnReplication="true" >mapSendOptions="6"/> > > > > > What may I be doing wrong ? Are you using sticky sessions on your load balancer? Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
backupManager - backup on all nodes and slowly
With below BackupManager backup manager configuration in server.xml heap memory increases over 100MB on each of four nodes in cluster. In addition time of ab -c 10 -n 10 -p post.txt http://localhost:18080/petclinic/session/fill is about 150 seconds with default DeltaManager it is about 15 seconds. What may I be doing wrong ? BR Jakub
