lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Updated] (SOLR-8914) inexplicable "no servers hosting shard: shard2" using MiniSolrCloudCluster
Date Tue, 29 Mar 2016 02:13:25 GMT


Hoss Man updated SOLR-8914:
    Attachment: live_nodes_mentions.log.txt

Attaching another interesting view: live_nodes_mentions.log.txt...

This is every log entry from ZkStateReader mentioning "live nodes" (not just "live nodes size",
so "Updated live nodes from ZooKeeper..." msgs also show up) distilled down to only the timestamp
port# (or TEST if it's from the main testing thread via MiniSolrCloudCluster or waitForRecoveries)
and log message.

Generated via...
grep -i "live nodes" jenkins.thetaphi.de_Lucene-Solr-6.x-Solaris_32.log.txt | perl -ple 's/.*2>
(\d+).*?(\[[^\]]*? \]) o.a.s.c.c.ZkStateReader(.*)/$1 $2 $3/; s/\[n:\d+)_solr\s*?\]/port
$1/; s/\[\s+\]/     TEST /' > live_nodes_mentions.log.txt
... use {{grep -v "port 63099"}} if you want to only focus on the nodes that host a piece
of the collection.

> inexplicable "no servers hosting shard: shard2" using MiniSolrCloudCluster
> --------------------------------------------------------------------------
>                 Key: SOLR-8914
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Hoss Man
>         Attachments: jenkins.thetaphi.de_Lucene-Solr-6.x-Solaris_32.log.txt, live_nodes_mentions.log.txt
> Jenkin's encountered a failure in TestTolerantUpdateProcessorCloud over the weekend....
> {noformat}
> Checking out Revision c46d7686643e7503304cb35dfe546bce9c6684e7 (refs/remotes/origin/branch_6x)
> Using Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseG1GC
> {noformat}
> The failure happened during the static setup of the test, when a MiniSolrCloudCluster
& several clients are initialized -- before any code related to TolerantUpdateProcessor
is ever used.
> I can't reproduce this, or really make sense of what i'm (not) seeing here in the logs,
so i'm filing this jira with my analysis in the hopes that someone else can help make sense
of it.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message