You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shawn Heisey (JIRA)" <ji...@apache.org> on 2015/10/05 17:48:27 UTC
[jira] [Commented] (SOLR-8127) Luke does not know about dynamic
fields on other shards fast enough
[ https://issues.apache.org/jira/browse/SOLR-8127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943555#comment-14943555 ]
Shawn Heisey commented on SOLR-8127:
------------------------------------
The actual Luke application is standalone Lucene-level program (separate from Solr) that can open a Lucene index. The Luke support in Solr is similar -- I believe that it only functions on the specific Lucene index stored in the shard replica that handles the request. It has absolutely no knowledge of what happens at the upper levels of Solr or SolrCloud. As far as I'm aware, it will never show you a dynamic field that is not explicitly present in the local Lucene index (shard replica).
I'm assuming that when you say "Luke" you are referring to the Luke request handler in Solr, not the separate Luke application.
What *may* be happening here, especially if your requests are being sent to the collection rather than a specific replica/shard, is that SolrCloud is bouncing your request between different shards and replicas within the collection, so the request may be handled by replica 1 of shard 1 on one attempt, then replica 3 of shard 7 on another attempt. If this is what is happening, then that field will only be present in the results if the request ends up on a replica for the specific shard containing the document with that field.
> Luke does not know about dynamic fields on other shards fast enough
> -------------------------------------------------------------------
>
> Key: SOLR-8127
> URL: https://issues.apache.org/jira/browse/SOLR-8127
> Project: Solr
> Issue Type: Bug
> Components: Schema and Analysis, SolrCloud
> Affects Versions: 4.10.2
> Environment: 3 shards
> Reporter: Alex K
> Labels: dynamic, luke, replication, sharding
>
> Add a document with a new (never seen before) dynamic field. It will not be visible through Luke requests on the other shards for quite a while, and there is no documentation regarding exactly how long it will take. The result is that a query to Luke must be made to every shard in the cluster if all dynamic fields are needed.
> All shards should be aware of a new dynamic field within seconds, if not milliseconds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org