[
https://issues.apache.org/jira/browse/SOLR-7421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14501397#comment-14501397
]
Shalin Shekhar Mangar commented on SOLR-7421:
---------------------------------------------
Thanks for looking into this, Tim.
This test was written to force flush a segment and then cause softCommit and
then trigger a full replication. In order to force flush a segment, the test
sets maxBufferedDocs to 2 which is why it creates so many files. Now that we
have the ability to change the peer sync limit via SOLR-6359, we should set the
limit to a small value (say n=4) and only add n+1 documents to simulate the
same behavior without creating such a lot of index files.
> RecoveryAfterSoftCommitTest fails frequently on Jenkins due to full index
> replication taking longer than 30 seconds
> -------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-7421
> URL: https://issues.apache.org/jira/browse/SOLR-7421
> Project: Solr
> Issue Type: Bug
> Reporter: Timothy Potter
> Attachments: RecoveryAfterSoftCommitTest_failure.log
>
>
> RecoveryAfterSoftCommitTest is failing frequently on Jenkins because the test
> only gives 30 seconds for the replica to recover after healing the partition.
> It looks like it's taking >30 seconds to replicate the full index from the
> leader (the test is designed so that peer sync can't work). It seems bad that
> it takes >30 seconds to replicate an index with only 115 documents in it ...
> wonder if there is cruft laying around from other tests? I've run beast on
> this test locally and it always passes. What's weird is I see log messages
> like:
> {code}
> [junit4] 2> 1436627 T4242 N:127.0.0.1:63274_ecb%2Fay C476
> oash.IndexFetcher.fetchLatestIndex Number of files in latest index in master:
> 263
> {code}
> 263 files for an index with 115 docs? Doesn't seem right!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
