[
https://issues.apache.org/jira/browse/SOLR-8586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419078#comment-15419078
]
Yago Riveiro edited comment on SOLR-8586 at 8/12/16 4:23 PM:
-------------------------------------------------------------
My index has 12T of data indexed with 4.0, the _version_ field only supports
docValues since 4.7.
To Upgrade to 5.x I ran the lucene-core-5.x over all my data,but with this new
feature I need to re-index all my data because I don't have docValues for
__version__ field and this feature use instead the un-inverted method that
creates a memory struct that doesn't fit the memory of my servers ...
To be honest, this never should be done in a minor release ... this mandatory
feature is based in a optional configuration :/
I will die in 5.4 or spend several months re-indexing data and figure out how
to update production without downtime. Not an easy task.
was (Author: yriveiro):
My index has 12T of data indexed with 4.0, the _version_ field only support
docValues since 4.7.
To Upgrade to 5.x I ran the lucene-core-5.x over all my data,but with this new
feature I need to re-index all my data because I don't have docValues for
__version__ field and this feature use instead the un-inverted method that
creates a memory struct that doesn't fit the memory of my servers ...
To be honest, this never should be done in a minor release ... this mandatory
feature is based in a optional configuration :/
I will die in 5.4 or spend several months re-indexing data and figure out how
to update production without downtime. Not an easy task.
> Implement hash over all documents to check for shard synchronization
> --------------------------------------------------------------------
>
> Key: SOLR-8586
> URL: https://issues.apache.org/jira/browse/SOLR-8586
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Yonik Seeley
> Assignee: Yonik Seeley
> Fix For: 5.5, 6.0
>
> Attachments: SOLR-8586.patch, SOLR-8586.patch, SOLR-8586.patch,
> SOLR-8586.patch
>
>
> An order-independent hash across all of the versions in the index should
> suffice. The hash itself is pretty easy, but we need to figure out
> when/where to do this check (for example, I think PeerSync is currently used
> in multiple contexts and this check would perhaps not be appropriate for all
> PeerSync calls?)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
