You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2019/04/03 18:07:00 UTC

[jira] [Reopened] (SOLR-13131) Category Routed Aliases

     [ https://issues.apache.org/jira/browse/SOLR-13131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hoss Man reopened SOLR-13131:
-----------------------------

Gus: The new CategoryRoutedAliasUpdateProcessorTest added in this jira is currently one of the most commonly failing test in our jenkins builds...

http://fucit.org/solr-jenkins-reports/failure-report.html
||Suite?||Class||Method||Rate||Runs||Fails||
|false|CategoryRoutedAliasUpdateProcessorTest|testSliceRouting|4.26439232409382|469|20|
|true|CategoryRoutedAliasUpdateProcessorTest|-|3.34928229665072|418|14|
|false|CategoryRoutedAliasUpdateProcessorTest|test|0.639658848614072|469|3|
|false|CategoryRoutedAliasUpdateProcessorTest|testMaxCardinality|0.427350427350427|468|2|
|false|CategoryRoutedAliasUpdateProcessorTest|testNonEnglish|0.427350427350427|468|2|
|false|CategoryRoutedAliasUpdateProcessorTest|testMustMatch|0.213675213675214|468|1|
|false|CategoryRoutedAliasUpdateProcessorTest|testInvalidMustMatch|0.213675213675214|468|1|

(some other night tests that run less often have a higher failure%, but in terms of raw numbers, this test is the biggest cause of when/why a jenkins buld fails)

Skimming the logs from some of these failures, a lot of the failures seem to ultimately relate to request timeouts wating for response from Solr - but skimming the logs suggests a host of assorted problems under the covers, from not being able to initialize cores, to assertion errors, to NPEs.

----

Are you looking into these failures? Do we have any sense of wether they are "test bugs" or "code bugs"?  should we role back this issue (at least on 8x) until we can get them under control?


> Category Routed Aliases
> -----------------------
>
>                 Key: SOLR-13131
>                 URL: https://issues.apache.org/jira/browse/SOLR-13131
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>    Affects Versions: master (9.0)
>            Reporter: Gus Heck
>            Assignee: Gus Heck
>            Priority: Major
>             Fix For: 8.1, master (9.0)
>
>         Attachments: indexingWithCRA.png, indexingwithoutCRA.png, indexintWithoutCRA2.png
>
>
> This ticket is to add a second type of routed alias in addition to the current time routed aliases. The new type of alias will allow data driven creation of collections based on the values of a field and automated organization of these collections under an alias that allows the collections to also be searched as a whole.
> The use case in mind at present is an IOT device type segregation, but I could also see this leading to the ability to direct updates to tenant specific hardware (in cooperation with autoscaling). 
> This ticket also looks forward to (but does not include) the creation of a Dimensionally Routed Alias which would allow organizing time routed data also segregated by device
> Further design details to be added in comments.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org