Re: ConcurrentModificationException in SolrInputDocument writeMap

Finally had a chance to get back to this and figured out what our problem was. Thanks to Mikhail for pointing me in the right direction. For some reason one of our custom UpdateRequestProcessors was calling super.processAdd as the first line in ou

Re: ConcurrentModificationException in SolrInputDocument writeMap

On 11/6/2019 8:17 AM, Tim Swetland wrote: I'm currently running into a ConcurrentModificationException ingesting data as we attempt to upgrade from Solr 8.1 to 8.2. It's not every document, but it definitely appears regularly in our logs. We didn't run into this problem in 8.1, so I'm not sure wh

Re: ConcurrentModificationException in SolrInputDocument writeMap

You probably hit https://issues.apache.org/jira/projects/SOLR/issues/SOLR-8028 Regards, Edward Em qua, 6 de nov de 2019 13:23, Mikhail Khludnev escreveu: > Hello, Tim. > Please confirm my understanding. Does exception happens in standalone Java > ingesting app? > If, it's so, Does it reuse ei

Re: ConcurrentModificationException in SolrInputDocument writeMap

Hello, Tim. Please confirm my understanding. Does exception happens in standalone Java ingesting app? If, it's so, Does it reuse either SolrInputDocument instances of fields/values collections between update calls? On Wed, Nov 6, 2019 at 8:00 AM Tim Swetland wrote: > Nevermind my comment on not

Re: ConcurrentModificationException in SolrInputDocument writeMap

Nevermind my comment on not having this problem in 8.1. We do have it there as well, I just didn't look far enough back in our logs on my initial search. Would still appreciate whatever thoughts anyone might have on the exception. On Wed, Nov 6, 2019 at 10:17 AM Tim Swetland wrote: > I'm current

RE: ConcurrentModificationException due to high volume of requests

Thank you Shalin. I've created SOLR-9414 KATHERINE MORA Senior Engineer -Original Message- From: Shalin Shekhar Mangar [mailto:shalinman...@gmail.com] Sent: Saturday, August 13, 2016 7:22 PM To: solr-user@lucene.apache.org Subject: Re: ConcurrentModificationException due to high v

Re: ConcurrentModificationException due to high volume of requests

This is a bug. Please open a Jira issue. We need to dig where else this param map is being used. It is possible that there are more such bugs. On Fri, Aug 12, 2016 at 10:57 PM, Katherine Mora < km...@searchtechnologies.com> wrote: > Hi All, > > We are using Solr 5.2.1 in a production environment

Re: ConcurrentModificationException from XMLResponseWriter

Shawn, We have custom search handlers that uses in built components - result and facet to generate the results. I see that our facet generation is using the LinkedHashMap. I will revisit my code. Thanks for the advise!!! We are migrating to Solr4 soon :) Thanks On Monday, November 25, 2013

Re: ConcurrentModificationException from XMLResponseWriter

On 11/25/2013 8:43 AM, Shyamsunder R Mutcha wrote: > > > Following exception is found in solr logs. We are using Solr 3.2. As the > stack trace is not referring to any application classes, I couldn't figure > out the piece of code that throws this exception. Is there any way to debug > this is

Re: ConcurrentModificationException in Solr 3.6.1

Hi There, I think Andre has already guided you in your earlier mail.. This should be fixed in 3.6.2 which is available since Dec 25. >From the r

Re: ConcurrentModificationException

On 2010-02-26 12:55 PM, Yonik Seeley wrote: Yep, definitely a bug. It looks like resourceLoader.newInstance() is fundamentally not thread safe. Could you open a JIRA issue for this? JIRA Issue opened: http://issues.apache.org/jira/browse/SOLR-1797 Dan

Re: ConcurrentModificationException

On 2010-02-26 12:55 PM, Yonik Seeley wrote: Yep, definitely a bug. It looks like resourceLoader.newInstance() is fundamentally not thread safe. -Yonik On Fri, Feb 26, 2010 at 2:48 PM, Yonik Seeley wrote: Could you open a JIRA issue for this? Yonik, Do you still need me to open a JIRA i

Re: ConcurrentModificationException

Yep, definitely a bug. It looks like resourceLoader.newInstance() is fundamentally not thread safe. -Yonik http://www.lucidimagination.com On Fri, Feb 26, 2010 at 2:48 PM, Yonik Seeley wrote: > Could you open a JIRA issue for this? > > After a quick look, it could be firstSearcher / newSearcher

Re: ConcurrentModificationException

Could you open a JIRA issue for this? After a quick look, it could be firstSearcher / newSearcher events that are being executed concurrently that change the list? Could you try commenting out firstSearcher/newSearcher events in solrconfig.xml and see if that fixes it? It could be that a lazy lo