You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by "Kelly, Frank" <fr...@here.com> on 2016/01/12 03:34:49 UTC
Solr 5.3.1 ArrayIndexOutOfBoundsException while running a query
Using Solr 5.3.1 in Solr Cloud mode deployed on AWS (each Solr instance has -Xmx 1024m and the server has 8GB of RAM)
Am getting a 500 error running a query via the UI
Looking in the logs I just see this with no stack trace
2016-01-12 02:04:22.181 ERROR (qtp59559151-7313) [c:qa_us-east-1_here_account18 s:shard2 r:core_node4 x:qa_us-east-1_here_account18_shard2_replica2] o.a.s.s.SolrDispatchFilter null:java.lang.ArrayIndexOutOfBoundsException
2016-01-12 02:04:22.201 ERROR (qtp59559151-7267) [c:qa_us-east-1_here_account18 s:shard2 r:core_node4 x:qa_us-east-1_here_account18_shard2_replica2] o.a.s.c.SolrCore java.lang.ArrayIndexOutOfBoundsException
I have examined the cluster state and there are no degraded shards.
I am suspicious that an OutOfMemoryError earlier in the day is still occurring but I have not seen one recently
solr_log_20160111_1510:java.lang.OutOfMemoryError: Java heap space
When I inspect the service status it seems to say I am OK for memory
[solr@qa-solr-us-east-1-4454eff7 logs]$ sudo service solr status
Found 1 Solr nodes:
Solr process 9641 running on port 8983
{
"solr_home":"/solr/data/",
"version":"5.3.1 1703449 - noble - 2015-09-17 01:48:15",
"startTime":"2016-01-11T15:10:14.113Z",
"uptime":"0 days, 11 hours, 22 minutes, 53 seconds",
"memory":"665.3 MB (%67.8) of 981.4 MB",
"cloud":{
"ZooKeeper":"ec2-54-173-143-61.compute-1.amazonaws.com:2181,ec2-52-90-213-206.compute-1.amazonaws.com:2181,ec2-52-90-108-64.compute-1.amazonaws.com:2181/solr",
"liveNodes":"3",
"collections":"56"}}
Any thoughts or suggestions on how to debug further (ideally get the stack trace)?
Thanks!
-Frank
[cid:372B00C7-E162-45EC-BA3E-64BC5D098016]
Frank Kelly
Principal Software Engineer
Predictive Analytics Team (SCBE/HAC/CDA)
HERE
5 Wayside Rd, Burlington, MA 01803, USA
42° 29' 7" N 71° 11' 32" W
[cid:2A590471-E354-4B0F-9393-C445DD4303A7]<http://360.here.com/> [cid:0346BFC6-3B91-40BD-8E7E-3D5E549E5516] <https://twitter.com/here> [cid:16238AC6-6A21-4C17-8990-07095FCED69A] <https://www.facebook.com/here> [cid:5773C34E-F274-464C-810C-B113E6299A56] <https://linkedin.com/company/heremaps> [cid:15654391-21A7-4012-8A18-A4589C8AEE4A] <https://www.instagram.com/here>
Re: Solr 5.3.1 ArrayIndexOutOfBoundsException while running a query
Posted by Erick Erickson <er...@gmail.com>.
The Solr logs should have a much more complete stack trace if you can
locate them.
1G of memory is very little for any serious Solr. I'm assuming you
restarted Solr after the
OOM, but Java isn't entirely reliable after an OOM.
FWIW,
Erick
On Mon, Jan 11, 2016 at 6:34 PM, Kelly, Frank <fr...@here.com> wrote:
> Using Solr 5.3.1 in Solr Cloud mode deployed on AWS (each Solr instance
> has –Xmx 1024m and the server has 8GB of RAM)
>
> Am getting a 500 error running a query via the UI
>
> Looking in the logs I just see this with no stack trace
>
> 2016-01-12 02:04:22.181 ERROR (qtp59559151-7313)
> [c:qa_us-east-1_here_account18 s:shard2 r:core_node4
> x:qa_us-east-1_here_account18_shard2_replica2] o.a.s.s.SolrDispatchFilter
> null:java.lang.ArrayIndexOutOfBoundsException
>
>
> 2016-01-12 02:04:22.201 ERROR (qtp59559151-7267)
> [c:qa_us-east-1_here_account18 s:shard2 r:core_node4
> x:qa_us-east-1_here_account18_shard2_replica2] o.a.s.c.SolrCore
> java.lang.ArrayIndexOutOfBoundsException
>
>
>
>
> I have examined the cluster state and there are no degraded shards.
> I am suspicious that an OutOfMemoryError earlier in the day is still
> occurring but I have not seen one recently
>
> solr_log_20160111_1510:java.lang.OutOfMemoryError: Java heap space
>
> When I inspect the service status it seems to say I am OK for memory
>
> [solr@qa-solr-us-east-1-4454eff7 logs]$ sudo service solr status
>
>
> Found 1 Solr nodes:
>
>
> Solr process 9641 running on port 8983
>
> {
>
> "solr_home":"/solr/data/",
>
> "version":"5.3.1 1703449 - noble - 2015-09-17 01:48:15",
>
> "startTime":"2016-01-11T15:10:14.113Z",
>
> "uptime":"0 days, 11 hours, 22 minutes, 53 seconds",
>
> "memory":"665.3 MB (%67.8) of 981.4 MB",
>
> "cloud":{
>
> "ZooKeeper":"ec2-54-173-143-61.compute-1.amazonaws.com:2181,
> ec2-52-90-213-206.compute-1.amazonaws.com:2181,
> ec2-52-90-108-64.compute-1.amazonaws.com:2181/solr",
>
> "liveNodes":"3",
>
> "collections":"56"}}
>
> Any thoughts or suggestions on how to debug further (ideally get the stack
> trace)?
>
> Thanks!
>
> -Frank
>
> *Frank Kelly*
>
> Principal Software Engineer
>
> Predictive Analytics Team (SCBE/HAC/CDA)
>
>
> *HERE *
>
> 5 Wayside Rd, Burlington, MA 01803, USA
>
> *42° 29' 7" N 71° 11' 32” W*
>
>
> <http://360.here.com/> <https://twitter.com/here>
> <https://www.facebook.com/here> <https://linkedin.com/company/heremaps>
> <https://www.instagram.com/here>
>
>