[
https://issues.apache.org/jira/browse/SOLR-7438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905473#comment-14905473
]
Mark Miller commented on SOLR-7438:
-----------------------------------
bq. // This is somewhat brittle, but current usage allows for it
Actually I don't think it does. I think this can create the opportunity for
false peery sync success. We have to do something else until truncate arrives.
I've discussed a possible workaround with Yonik and have been testing it.
> Look into using new HDFS truncate feature in HdfsTransactionLog.
> ----------------------------------------------------------------
>
> Key: SOLR-7438
> URL: https://issues.apache.org/jira/browse/SOLR-7438
> Project: Solr
> Issue Type: Improvement
> Reporter: Mark Miller
> Assignee: Mark Miller
>
> Looks like truncate is added in 2.7.
> See HdfsTransactionLog:
> {code}
> // HACK
> // while waiting for HDFS-3107, instead of quickly
> // dropping, we slowly apply
> // This is somewhat brittle, but current usage
> // allows for it
> @Override
> public boolean dropBufferedUpdates() {
> Future<RecoveryInfo> future = applyBufferedUpdates();
> if (future != null) {
> try {
> future.get();
> } catch (InterruptedException | ExecutionException e) {
> throw new RuntimeException(e);
> }
> }
> return true;
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
