Re: Error about setting up solr instances

2012-05-07 Thread Otis Gospodnetic
Hi Emma,

This isn't really Solr-specific... I'd Google that instead or ask on OpenJDK 
mailing list.

Otis

Performance Monitoring for Solr / ElasticSearch / HBase - 
http://sematext.com/spm 




 From: Emma Bo Liu smile.emma1...@gmail.com
To: solr-user@lucene.apache.org 
Sent: Monday, May 7, 2012 4:50 PM
Subject: Error about setting up solr instances
 
I am trying to set up 60 solr instances.But the instances can only be set
up until the fifth one. The error is as follows



*OpenJDK 64-Bit Server VM warning: Insufficient space for shared memory
file:*

*   /tmp/hsperfdata_eliu/26268*

*Try using the -Djava.io.tmpdir= option to select an alternate temp location
*.



2012-05-07 16:31:08.172:INFO:oejs.Server:jetty-8.1.2.v20120308

2012-05-07 16:31:08.224:INFO:oejdp.ScanningAppProvider:Deployment monitor
/usr/apache-solr-4.0-2012-05-07_08-24-29/example5/webapps at interval 0

2012-05-07 16:31:08.272:INFO:oejd.DeploymentManager:Deployable added:
/usr/apache-solr-4.0-2012-05-07_08-24-29/example5/webapps/solr.war

2012-05-07 16:31:08.366:WARN:oejw.WebAppContext:Failed startup of context
o.e.j.w.WebAppContext{/solr,null},/usr/apache-solr-4.0-2012-05-07_08-24-29/example5/webapps/solr.war

java.lang.IllegalArgumentException: *Bad temp directory:
/tmp/JettyContext133145981097751551*



Though it is the warning but the first 4 ones works well and they didn't
get the error. Does anybody know how to solve it? Thanks



Emma




Re: Error about setting up solr instances

2012-05-07 Thread Lance Norskog
This may be an issue with the Memory-Mapped Directory. This opens all
files and allocates VM space (but not actual memory) for each entire
file. One thing I've noticed is that there can be a lot of open file
descriptors for the index, far more than make sense. You may be going
out of the allocatable virtual memory space (not the physical memory
of the server).

There is an alternate Directory implementation called the
NIOFSDirectory. This may work better for you. Here is where you set
the Directory implementation in solrconfig.xml:

--
  !-- The DirectoryFactory to use for indexes.

   solr.StandardDirectoryFactory, the default, is filesystem
   based and tries to pick the best implementation for the current
   JVM and platform.  One can force a particular implementation
   via solr.MMapDirectoryFactory, solr.NIOFSDirectoryFactory, or
   solr.SimpleFSDirectoryFactory.

   solr.RAMDirectoryFactory is memory based, not
   persistent, and doesn't work with replication.
--
  directoryFactory name=DirectoryFactory

class=${solr.directoryFactory:solr.StandardDirectoryFactory}/

-
But one must ask: why do you need 60 separate JVMs running the same program?



On Mon, May 7, 2012 at 3:54 PM, Otis Gospodnetic
otis_gospodne...@yahoo.com wrote:
 Hi Emma,

 This isn't really Solr-specific... I'd Google that instead or ask on OpenJDK 
 mailing list.

 Otis
 
 Performance Monitoring for Solr / ElasticSearch / HBase - 
 http://sematext.com/spm




 From: Emma Bo Liu smile.emma1...@gmail.com
To: solr-user@lucene.apache.org
Sent: Monday, May 7, 2012 4:50 PM
Subject: Error about setting up solr instances

I am trying to set up 60 solr instances.But the instances can only be set
up until the fifth one. The error is as follows



*OpenJDK 64-Bit Server VM warning: Insufficient space for shared memory
file:*

*   /tmp/hsperfdata_eliu/26268*

*Try using the -Djava.io.tmpdir= option to select an alternate temp location
*.



2012-05-07 16:31:08.172:INFO:oejs.Server:jetty-8.1.2.v20120308

2012-05-07 16:31:08.224:INFO:oejdp.ScanningAppProvider:Deployment monitor
/usr/apache-solr-4.0-2012-05-07_08-24-29/example5/webapps at interval 0

2012-05-07 16:31:08.272:INFO:oejd.DeploymentManager:Deployable added:
/usr/apache-solr-4.0-2012-05-07_08-24-29/example5/webapps/solr.war

2012-05-07 16:31:08.366:WARN:oejw.WebAppContext:Failed startup of context
o.e.j.w.WebAppContext{/solr,null},/usr/apache-solr-4.0-2012-05-07_08-24-29/example5/webapps/solr.war

java.lang.IllegalArgumentException: *Bad temp directory:
/tmp/JettyContext133145981097751551*



Though it is the warning but the first 4 ones works well and they didn't
get the error. Does anybody know how to solve it? Thanks



Emma






-- 
Lance Norskog
goks...@gmail.com