[
https://issues.apache.org/jira/browse/SOLR-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096285#comment-14096285
]
Hoss Man edited comment on SOLR-2894 at 8/13/14 11:26 PM:
----------------------------------------------------------
Spooky ... that seed doesn't reproduce for me - even though the failure looks
like something that should definitely be related to pivot code, and not any
sort of random query timeout or async logic that might be diff between diff
runs/machines.
[[email protected]]: does this seed's failure reproduce reliably for you?
for context here's the seed/failure from the log mark attached...
{noformat}
[junit4] 2> NOTE: reproduce with: ant test -Dtestcase=TestCloudPivotFacet
-Dtests.method=testDistribSearch -Dtests.seed=A9A19A1033FB57AD
-Dtests.slow=true -Dtests.locale=sr__#Latn -Dtests.timezone=Europe/Helsinki
-Dtests.file.encoding=UTF-8
[junit4] FAILURE 43.2s J3 | TestCloudPivotFacet.testDistribSearch <<<
[junit4] > Throwable #1: java.lang.AssertionError:
{main(facet=true&facet.pivot=pivot_i1%2Cbogus_not_in_any_doc_s%2Cpivot_l&facet.limit=17&facet.missing=true&facet.sort=index&facet.overrequest.ratio=0.63600624),extra(rows=0&q=id%3A%5B*+TO+511%5D&_test_miss=true&_test_sort=index)}
==> pivot_i1,bogus_not_in_any_doc_s,pivot_l:
{params(rows=0),defaults({main({main({main(rows=0&q=id%3A%5B*+TO+511%5D&_test_miss=true&_test_sort=index),extra(fq=-pivot_i1%3A%5B*+TO+*%5D)}),extra(fq=-bogus_not_in_any_doc_s%3A%5B*+TO+*%5D)}),extra(fq=-pivot_l%3A%5B*+TO+*%5D)})}
expected:<18> but was:<16>
[junit4] > at
__randomizedtesting.SeedInfo.seed([A9A19A1033FB57AD:2847140844A43791]:0)
[junit4] > at
org.apache.solr.cloud.TestCloudPivotFacet.assertPivotCountsAreCorrect(TestCloudPivotFacet.java:248)
[junit4] > at
org.apache.solr.cloud.TestCloudPivotFacet.doTest(TestCloudPivotFacet.java:195)
[junit4] > at
org.apache.solr.BaseDistributedSearchTestCase.testDistribSearch(BaseDistributedSearchTestCase.java:865)
[junit4] > at java.lang.Thread.run(Thread.java:744)
[junit4] > Caused by: java.lang.AssertionError:
pivot_i1,bogus_not_in_any_doc_s,pivot_l:
{params(rows=0),defaults({main({main({main(rows=0&q=id%3A%5B*+TO+511%5D&_test_miss=true&_test_sort=index),extra(fq=-pivot_i1%3A%5B*+TO+*%5D)}),extra(fq=-bogus_not_in_any_doc_s%3A%5B*+TO+*%5D)}),extra(fq=-pivot_l%3A%5B*+TO+*%5D)})}
expected:<18> but was:<16>
[junit4] > at
org.apache.solr.cloud.TestCloudPivotFacet.assertNumFound(TestCloudPivotFacet.java:521)
[junit4] > at
org.apache.solr.cloud.TestCloudPivotFacet.assertPivotCountsAreCorrect(TestCloudPivotFacet.java:269)
[junit4] > at
org.apache.solr.cloud.TestCloudPivotFacet.assertPivotCountsAreCorrect(TestCloudPivotFacet.java:280)
[junit4] > at
org.apache.solr.cloud.TestCloudPivotFacet.assertPivotCountsAreCorrect(TestCloudPivotFacet.java:280)
[junit4] > at
org.apache.solr.cloud.TestCloudPivotFacet.assertPivotCountsAreCorrect(TestCloudPivotFacet.java:238)
[junit4] > ... 42 more
{noformat}
*EDIT:* I forgot to mention that i did confirm that based on comparing mark's
logs with my own, the seed in question did reproduce the same numDocs and same
random pivot params (so presumably it produced the same index in between) ..
one potentially interesting thing to note is that the failure mark gets is on
the first random pivot request executed.
The failure message indicates that when looking at the nested "facet.missing"
counts (ie: docs that didn't have a value in any of hte 3 specified fields
fields) there were only 16 docs found by doing a filtered query, but the
initial facet.pivot query said there should be 18. If those numbers were
reversed, i might guess maybe the discrepency was a timing issue of some docs
being visible on some replicas when the first facet.pivot query was executed,
but where later during the sanity check query -- but i can't imagine how the
number of matching odcs would go _down_ (at least not in any way that wouldn't
reproduce reliably)
was (Author: hossman):
Spooky ... that seed doesn't reproduce for me - even though the failure looks
like something that should definitely be related to pivot code, and not any
sort of random query timeout or async logic that might be diff between diff
runs/machines.
[[email protected]]: does this seed's failure reproduce reliably for you?
for context here's the seed/failure from the log mark attached...
{noformat}
[junit4] 2> NOTE: reproduce with: ant test -Dtestcase=TestCloudPivotFacet
-Dtests.method=testDistribSearch -Dtests.seed=A9A19A1033FB57AD
-Dtests.slow=true -Dtests.locale=sr__#Latn -Dtests.timezone=Europe/Helsinki
-Dtests.file.encoding=UTF-8
[junit4] FAILURE 43.2s J3 | TestCloudPivotFacet.testDistribSearch <<<
[junit4] > Throwable #1: java.lang.AssertionError:
{main(facet=true&facet.pivot=pivot_i1%2Cbogus_not_in_any_doc_s%2Cpivot_l&facet.limit=17&facet.missing=true&facet.sort=index&facet.overrequest.ratio=0.63600624),extra(rows=0&q=id%3A%5B*+TO+511%5D&_test_miss=true&_test_sort=index)}
==> pivot_i1,bogus_not_in_any_doc_s,pivot_l:
{params(rows=0),defaults({main({main({main(rows=0&q=id%3A%5B*+TO+511%5D&_test_miss=true&_test_sort=index),extra(fq=-pivot_i1%3A%5B*+TO+*%5D)}),extra(fq=-bogus_not_in_any_doc_s%3A%5B*+TO+*%5D)}),extra(fq=-pivot_l%3A%5B*+TO+*%5D)})}
expected:<18> but was:<16>
[junit4] > at
__randomizedtesting.SeedInfo.seed([A9A19A1033FB57AD:2847140844A43791]:0)
[junit4] > at
org.apache.solr.cloud.TestCloudPivotFacet.assertPivotCountsAreCorrect(TestCloudPivotFacet.java:248)
[junit4] > at
org.apache.solr.cloud.TestCloudPivotFacet.doTest(TestCloudPivotFacet.java:195)
[junit4] > at
org.apache.solr.BaseDistributedSearchTestCase.testDistribSearch(BaseDistributedSearchTestCase.java:865)
[junit4] > at java.lang.Thread.run(Thread.java:744)
[junit4] > Caused by: java.lang.AssertionError:
pivot_i1,bogus_not_in_any_doc_s,pivot_l:
{params(rows=0),defaults({main({main({main(rows=0&q=id%3A%5B*+TO+511%5D&_test_miss=true&_test_sort=index),extra(fq=-pivot_i1%3A%5B*+TO+*%5D)}),extra(fq=-bogus_not_in_any_doc_s%3A%5B*+TO+*%5D)}),extra(fq=-pivot_l%3A%5B*+TO+*%5D)})}
expected:<18> but was:<16>
[junit4] > at
org.apache.solr.cloud.TestCloudPivotFacet.assertNumFound(TestCloudPivotFacet.java:521)
[junit4] > at
org.apache.solr.cloud.TestCloudPivotFacet.assertPivotCountsAreCorrect(TestCloudPivotFacet.java:269)
[junit4] > at
org.apache.solr.cloud.TestCloudPivotFacet.assertPivotCountsAreCorrect(TestCloudPivotFacet.java:280)
[junit4] > at
org.apache.solr.cloud.TestCloudPivotFacet.assertPivotCountsAreCorrect(TestCloudPivotFacet.java:280)
[junit4] > at
org.apache.solr.cloud.TestCloudPivotFacet.assertPivotCountsAreCorrect(TestCloudPivotFacet.java:238)
[junit4] > ... 42 more
{noformat}
> Implement distributed pivot faceting
> ------------------------------------
>
> Key: SOLR-2894
> URL: https://issues.apache.org/jira/browse/SOLR-2894
> Project: Solr
> Issue Type: Improvement
> Reporter: Erik Hatcher
> Assignee: Hoss Man
> Fix For: 4.9, 5.0
>
> Attachments: SOLR-2894-mincount-minification.patch,
> SOLR-2894-reworked.patch, SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch,
> SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch,
> SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch,
> SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch,
> SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch,
> SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch,
> SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch,
> SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch,
> SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch,
> SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch,
> SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch,
> SOLR-2894.patch, SOLR-2894.patch, SOLR-2894_cloud_test.patch,
> dateToObject.patch, pivot_mincount_problem.sh, pivotfail.log
>
>
> Following up on SOLR-792, pivot faceting currently only supports
> undistributed mode. Distributed pivot faceting needs to be implemented.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
