[ 
https://issues.apache.org/jira/browse/SOLR-7954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710599#comment-14710599
 ] 

Modassar Ather commented on SOLR-7954:
--------------------------------------

To add to the summary and description.

I changed the {noformat}doc.addField("colid", "val!"+i+"!-"+"ref"+i);{noformat} 
to {noformat}doc.addField("colid", "val"+i+"!-"+"ref"+i);{noformat}
The documents got distributed to all the nodes. I indexed 1 million documents 
and was able to reproduce the issue. All the shards had around 200000 documents 
each.
Later I indexed 400000 documents on which I could not reproduce it. All the 
shards had around 100000 documents each.
There are 4 shards with no replica on my test environment.

> ArrayIndexOutOfBoundsException from distributed HLL serialization logic when 
> using using stats.field={!cardinality=1.0} in a distributed query
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-7954
>                 URL: https://issues.apache.org/jira/browse/SOLR-7954
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 5.2.1
>         Environment: SolrCloud 4 node cluster.
> Ubuntu 12.04
> OS Type 64 bit
>            Reporter: Modassar Ather
>            Assignee: Hoss Man
>         Attachments: SOLR-7954.patch
>
>
> User reports indicate that using {{stats.field=\{!cardinality=1.0\}foo}} on a 
> field that has extremely high cardinality on a single shard (example: 150K 
> unique values) can lead to "ArrayIndexOutOfBoundsException: 3" on the shard 
> during serialization of the HLL values.
> using "cardinality=0.9" (or lower) doesn't produce the same symptoms, 
> suggesting the problem is specific to large log2m and regwidth values.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to