On 4/22/2014 1:28 AM, Atanas Atanasov wrote:
> Just a clarification if someone decides to reproduce it:
> 1. 64 bit apache tomcat installation (7 or 8) -> solr 4.4 deployed, any JVM.
> 2. Create 1000 cores.
> 3. Restart Apache Tomcat.
> 4. Create 1 core.
>
> I hope I explained it well, if not just
Hi to all,
I have some other information that might be useful. Installing previous
java did not work. The creation of a core does not take 20 minutes,
it seems that it happens right away but there is no response and looks
stuck. After I restart the apache tomcat
the core is there and working witho
Hello again,
Current situation is, after setting the two options in order not to load
the cores on start up
and ramBufferSizeMB=32 Tomcat is stable, responsive, threads reach 60 as a
maximum.
Browsing and storing are fast. I should note that I have many cores with
small amount of documents.
Unfort
On 4/10/2014 12:40 AM, Atanas Atanasov wrote:
> I need some help. After updating to SOLR 4.4 the tomcat process is
> consuming about 2GBs of memory, the CPU usage is about 40% after the start
> for about 10 minutes. However, the bigger problem is, I have about 1000
> cores and seems that for each c
OKay okay i am a centos user in office, windows at home :D
Thanks
Aman Tandon
On Thu, Apr 10, 2014 at 8:01 PM, Atanas Atanasov wrote:
> Hi,
>
> I see the threads of the tomcat7.exe process in the Windows Task manager.
>
> Regards,
> Atanas Atanasov
>
>
> On Thu, Apr 10, 2014 at 5:28 PM, Aman Ta
Hi,
I see the threads of the tomcat7.exe process in the Windows Task manager.
Regards,
Atanas Atanasov
On Thu, Apr 10, 2014 at 5:28 PM, Aman Tandon wrote:
> Hi Atanas,
>
> I have a question that, how do know that how much thread does the tomcat
> has?
>
> Thanks
> Aman Tandon
>
>
> On Thu, Apr
Hi Atanas,
I have a question that, how do know that how much thread does the tomcat
has?
Thanks
Aman Tandon
On Thu, Apr 10, 2014 at 7:53 PM, Erick Erickson wrote:
> I don't expect having equal values to make a noticeable difference,
> except possibly in some corner cases. Setting them equal is
I don't expect having equal values to make a noticeable difference,
except possibly in some corner cases. Setting them equal is mostly for
avoiding surprises...
Erick
On Thu, Apr 10, 2014 at 7:17 AM, Atanas Atanasov wrote:
> Thanks for the tip,
>
> I already set the core properties. Now tomcat h
Thanks for the tip,
I already set the core properties. Now tomcat has only 27 threads after
start up, which is awesome.
Works fine, first search is not noticeably slower than before.
I'll put equal values for Xmx and Xms and see if there will be any
difference.
Regards,
Atanas
On Thu, Apr 10, 2
Trying to fit 1,000 cores in 6G of memory is... interesting. That's a
lot of stuff in a small amount of memory. I hope these cores' indexes
are tiny.
The lazy-loading bit for cores has a price. The first user in will pay
the warmup penalty for that core while it loads. This may or may not
be notic
On Thu, Apr 10, 2014 at 2:14 PM, Atanas Atanasov wrote:
> SEVERE: null:ClientAbortException: java.net.SocketException: Software
> caused connection abort: socket write error
Separate issue, but most likely the client closed the browser and the
server had nowhere to send the respond too. So, it c
Thanks for the quick responses,
I have allocated 1GB min and 6 GB max memory to Java. The cache settings
are the default ones (maybe this is a good point to start).
All cores share the same schema and config.
I'll try setting the
loadOnStartup=*false* transient=*true *options for each core and see
Are you using all those cores at once? If not, there is a recent
settings to allow solr to load cores on demand.
If you are using them all, perhaps you need to look into splitting
them to different machines (horizontal scaling).
What about your caches? How many additional structures you have
conf
I guess this is definitely due to the firstsearcher defined in
solrconfig.xml, you must make some tweaks in that I hope it will help. We
are using the same typo which you just mentioned here but we are using the
indexing server separately and replicating data to our other two server so
that it won'
Hi, guys,
I need some help. After updating to SOLR 4.4 the tomcat process is
consuming about 2GBs of memory, the CPU usage is about 40% after the start
for about 10 minutes. However, the bigger problem is, I have about 1000
cores and seems that for each core a thread is created. The process has
mo
15 matches
Mail list logo
