[ https://issues.apache.org/jira/browse/SOLR-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14263763#comment-14263763 ]
Forest Soup commented on SOLR-6359: ----------------------------------- it works but with some pre-condition: the 20% newest existing transaction log of the core to be recovered must be newer than the 20% oldest existing transaction log of the good core. > Allow customization of the number of records and logs kept by UpdateLog > ----------------------------------------------------------------------- > > Key: SOLR-6359 > URL: https://issues.apache.org/jira/browse/SOLR-6359 > Project: Solr > Issue Type: Improvement > Reporter: Ramkumar Aiyengar > Assignee: Mark Miller > Priority: Minor > Fix For: 5.0, Trunk > > > Currently {{UpdateLog}} hardcodes the number of logs and records it keeps, > and the hardcoded numbers (100 records, 10 logs) can be quite low (esp. the > records) in an heavily indexing setup, leading to full recovery even if Solr > was just stopped and restarted. > These values should be customizable (even if only present as expert options). -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org