[ https://issues.apache.org/jira/browse/SOLR-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Drob updated SOLR-7734: ---------------------------- Attachment: SOLR-7734.patch New patch that moves the {{System.setProperty}} calls out of {{SolrRecordWriter}}, since we explicitly control the configuration now. Also, disabled nrt cache and block cache, since there is a single write and no reads in the MR job. > MapReduce Indexer can error when using collection > ------------------------------------------------- > > Key: SOLR-7734 > URL: https://issues.apache.org/jira/browse/SOLR-7734 > Project: Solr > Issue Type: Bug > Components: contrib - MapReduce > Affects Versions: 5.2.1 > Reporter: Mike Drob > Fix For: 5.3, Trunk > > Attachments: SOLR-7734.patch, SOLR-7734.patch > > > When running the MapReduceIndexerTool, it will usually pull a > {{solrconfig.xml}} from ZK for the collection that it is running against. > This can be problematic for several reasons: > * Performance: The configuration in ZK will likely have several query > handlers, and lots of other components that don't make sense in an > indexing-only use of EmbeddedSolrServer (ESS). > * Classpath Resources: If the Solr services are using some kind of additional > service (such as Sentry for auth) then the indexer will not have access to > the necessary configurations without the user jumping through several hoops. > * Distinct Configuration Needs: Enabling Soft Commits on the ESS doesn't make > sense. There's other configurations that > * Update Chain Behaviours: I'm under the impression that UpdateChains may > behave differently in ESS than a SolrCloud cluster. Is it safe to depend on > consistent behaviour here? -- 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