Yes, it´s an XY problem :)
We are making the first tests to split our shard (Solr 5.1)
The problem we have is this: the number of documents indexed in the new
shards is lower than in the original one (19814 and 19653, vs 61100), and
always the same. We have no idea why Solr is doing this. A problem with
some documents, with the segment?
A long time after we changed from "normal" Solr to Solr Cloud, we found
that the parameter "router" in clusterstate.json was incorrect, because we
wanted to have "compositeId" and it was set as "explicit". The solution
was deleting the clusterstate.json and restart Solr. And we are thinking
that maybe the problem with the SPLIT is related with that: some documents
are stored with the hash value and others not, and SPLIT needs that to
distribute them. But I know that this likely has nothing to do with the
SPLIT problem, it's only an idea.
This is the log, all seem to be normal:
INFO - 2015-08-26 09:13:47.654;
org.apache.solr.handler.admin.CoreAdminHandler; Invoked split action for
core: buscon
INFO - 2015-08-26 09:13:47.656;
org.apache.solr.update.DirectUpdateHandler2; start
commit{,optimize=false,openSearcher=true,
waitSearcher=true,expungeDeletes=false,softCommit=false,prepareCommit=false}
INFO - 2015-08-26 09:13:47.656;
org.apache.solr.update.DirectUpdateHandler2; No uncommitted changes.
Skipping IW.commit.
INFO - 2015-08-26 09:13:47.657; org.apache.solr.core.SolrCore;
SolrIndexSearcher has not changed - not re-opening: org.apach
e.solr.search.SolrIndexSearcher
INFO - 2015-08-26 09:13:47.657;
org.apache.solr.update.DirectUpdateHandler2; end_commit_flush
INFO - 2015-08-26 09:13:47.658; org.apache.solr.update.SolrIndexSplitter;
SolrIndexSplitter: partitions=2 segments=1
INFO - 2015-08-26 09:13:47.922; org.apache.solr.update.SolrIndexSplitter;
SolrIndexSplitter: partition #0 partitionCount=2 r
ange=0-3fffffff
INFO - 2015-08-26 09:13:47.922; org.apache.solr.update.SolrIndexSplitter;
SolrIndexSplitter: partition #0 partitionCount=2 r
ange=0-3fffffff segment #0 segmentCount=1
INFO - 2015-08-26 09:22:19.533; org.apache.solr.update.SolrIndexSplitter;
SolrIndexSplitter: partition #1 partitionCount=2 r
ange=40000000-7fffffff
INFO - 2015-08-26 09:22:19.536; org.apache.solr.update.SolrIndexSplitter;
SolrIndexSplitter: partition #1 partitionCount=2 r
ange=40000000-7fffffff segment #0 segmentCount=1
INFO - 2015-08-26 09:30:44.141;
org.apache.solr.servlet.SolrDispatchFilter; [admin] webapp=null
path=/admin/cores params={ta
rgetCore=buscon_shard2_0_replica1&targetCore=buscon_shard2_1_replica1&action=SPLIT&core=buscon&wt=javabin&qt=/admin/cores&ver
sion=2} status=0 QTime=1016486
INFO - 2015-08-26 09:30:44.387;
org.apache.solr.handler.admin.CoreAdminHandler; Applying buffered updates
on core: buscon_sh
ard2_0_replica1
INFO - 2015-08-26 09:30:44.387;
org.apache.solr.handler.admin.CoreAdminHandler; No buffered updates
available. core=buscon_s
hard2_0_replica1
INFO - 2015-08-26 09:30:44.388;
org.apache.solr.servlet.SolrDispatchFilter; [admin] webapp=null
path=/admin/cores params={na
me=buscon_shard2_0_replica1&action=REQUESTAPPLYUPDATES&wt=javabin&qt=/admin/cores&version=2}
status=0 QTime=2
INFO - 2015-08-26 09:30:44.441;
org.apache.solr.handler.admin.CoreAdminHandler; Applying buffered updates
on core: buscon_sh
ard2_1_replica1
INFO - 2015-08-26 09:30:44.441;
org.apache.solr.handler.admin.CoreAdminHandler; No buffered updates
available. core=buscon_s
hard2_1_replica1
INFO - 2015-08-26 09:30:44.441;
org.apache.solr.servlet.SolrDispatchFilter; [admin] webapp=null
path=/admin/cores params={na
me=buscon_shard2_1_replica1&action=REQUESTAPPLYUPDATES&wt=javabin&qt=/admin/cores&version=2}
status=0 QTime=0
INFO - 2015-08-26 09:30:44.743;
org.apache.solr.common.cloud.ZkStateReader$2; A cluster state change:
WatchedEvent state:Syn
cConnected type:NodeDataChanged path:/clusterstate.json, has occurred -
updating... (live nodes size: 4)
Thanks,
David
De: Anshum Gupta <ans...@anshumgupta.net>
Para: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org>,
Fecha: 26/08/2015 10:27
Asunto: Re: Hash of solr documents
Hi David,
The route key itself is indexed, but not the hash value. Why do you need
to
know and display the hash value? This seems like an XY problem to me:
http://people.apache.org/~hossman/#xyproblem
On Wed, Aug 26, 2015 at 1:17 AM, <david.dav...@correo.aeat.es> wrote:
> Hi,
>
> I have read in one post in the Internet that the hash Solr Cloud
> calculates over the key field to send each document to a different shard
> is indexed. Is this true? If true, is there any way to show this hash
for
> each document?
>
> Thanks,
>
> David
--
Anshum Gupta
