[Dspace-tech] Increase in lo Traffic Since 3.1 Upgrade
I don't suppose this is normal, so I'd appreciate any hints on what might be going wrong here. Since upgrading to DSpace 3.1 (from 3.0 -- I think) and Tomcat 7 (from 6) during the first week of April, traffic on lo has increased enormously: Fortunately, traffic on eth0 has not increased like that: And there are no other interfaces available. I am using Apache's mod_proxy, so I expect traffic on 127.0.0.1 being sent to/from port 8009, but this much? Have I misconfigured something? Sean -- -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Increase in lo Traffic Since 3.1 Upgrade
Hi Sean, DSpace 3.1 is just a bugfix relase for 3.0, so that's hardly the source of the increase. It will be something else you did while doing the upgrade. Perhaps you started using either Discovery or the new OAI. Most importantly, DSpace uses the loopback interface to communicate with Solr, which contains three cores: statistics (Solr statistics since about 1.6), search (Discovery since 1.7 for XMLUI, optional for 3.0 JSPUI) and oai (OAI since 3.0). You can tell the Solr traffic apart from your AJP (mod_proxy) traffic by port - Solr is listening on 8080 by default, while AJP is listening on 8009 by default. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Increase in lo Traffic Since 3.1 Upgrade
On 31 May 2013 10:10, helix84 heli...@centrum.sk wrote: DSpace 3.1 is just a bugfix relase for 3.0, so that's hardly the source of the increase. It will be something else you did while doing the upgrade. Perhaps you started using either Discovery or the new OAI. Sorry, the upgrade was from DSpace 1.8. I had been using Discovery previously. Most importantly, DSpace uses the loopback interface to communicate with Solr, which contains three cores: statistics (Solr statistics since about 1.6), search (Discovery since 1.7 for XMLUI, optional for 3.0 JSPUI) and oai (OAI since 3.0). You can tell the Solr traffic apart from your AJP (mod_proxy) traffic by port - Solr is listening on 8080 by default, while AJP is listening on 8009 by default. I have been using tcpdump to watch traffic on 127.0.0.1 and, if I filter out ports 8080 and 8009, there still seems to be a lot of traffic on high ports like 5432, e.g.: 10:49:43.033658 IP 127.0.0.1.5432 127.0.0.1.59774: Flags [P.], seq 2408616:2408681, ack 99884, win 2048, options [nop,nop,TS val 46007271 ecr 46007271], length 65 10:49:43.054594 IP 127.0.0.1.59774 127.0.0.1.5432: Flags [P.], seq 99884:99930, ack 2408681, win 5128, options [nop,nop,TS val 46007276 ecr 46007271], length 46 10:49:43.054882 IP 127.0.0.1.5432 127.0.0.1.59774: Flags [P.], seq 2408681:2408746, ack 99930, win 2048, options [nop,nop,TS val 46007276 ecr 46007276], length 65 10:49:43.062522 IP 127.0.0.1.59774 127.0.0.1.5432: Flags [P.], seq 99930:99976, ack 2408746, win 5128, options [nop,nop,TS val 46007278 ecr 46007276], length 46 10:49:43.062716 IP 127.0.0.1.5432 127.0.0.1.59774: Flags [P.], seq 2408746:2408811, ack 99976, win 2048, options [nop,nop,TS val 46007278 ecr 46007278], length 65 10:49:43.070403 IP 127.0.0.1.59774 127.0.0.1.5432: Flags [P.], seq 99976:100022, ack 2408811, win 5128, options [nop,nop,TS val 46007280 ecr 46007278], length 46 10:49:43.070568 IP 127.0.0.1.5432 127.0.0.1.59774: Flags [P.], seq 2408811:2408876, ack 100022, win 2048, options [nop,nop,TS val 46007280 ecr 46007280], length 65 10:49:43.083987 IP 127.0.0.1.59774 127.0.0.1.5432: Flags [P.], seq 100022:100053, ack 2408876, win 5128, options [nop,nop,TS val 46007284 ecr 46007280], length 31 I suppose I need to shut down tomcat and see if this continues, but this is a production server. If I were to firewall off all ports above 5000 on the lo interface, this should not have any impact on DSpace? I tried that and couldn't access the site. Sean -- -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Increase in lo Traffic Since 3.1 Upgrade
On Fri, May 31, 2013 at 10:59 AM, Sean Carte sean.ca...@gmail.com wrote: I suppose I need to shut down tomcat and see if this continues, but this is a production server. If I were to firewall off all ports above 5000 on the lo interface, this should not have any impact on DSpace? I tried that and couldn't access the site. 5432 is postgres... Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Increase in lo Traffic Since 3.1 Upgrade
On 31 May 2013 11:04, helix84 heli...@centrum.sk wrote: On Fri, May 31, 2013 at 10:59 AM, Sean Carte sean.ca...@gmail.com wrote: I suppose I need to shut down tomcat and see if this continues, but this is a production server. If I were to firewall off all ports above 5000 on the lo interface, this should not have any impact on DSpace? I tried that and couldn't access the site. 5432 is postgres... I thought that seemed familiar. Thanks! I just installed another server and clicked on a few browse links and racked up 81MB on lo. So I suppose this is normal. Thanks for the feedback, Ivan. Sean -- -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
