[
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
Updated patch:
* Fixed imports.
* Used try-with-resources for streams.
* Fixed file location.
* Updated Lucene match version.
* Removed request dispatcher section
I don't have a good answer for what to do with the docs. Trying to enumerate
all the possibilities - use embedded solrconfig, use solrconfig from zk, use
solrconfig from solr home dir, got really messy, so I tried to hedge. I'm now
leaning toward it being worth the additional complexity in documentation to
spell everything out explicitly but don't have a good handle on it.
I'm not sure about working with managed schemas. I can remove the comment to
prevent confusion - it was originally copied from another example file.
JMX on MapReduce tasks can be enabled through {{mapreduce.map.java.opts}} -
I've seen it used for attempting to monitor memory usage. If somebody wants to
try to do this, then I don't intend to give them more hoops to jump through. If
jmx is disabled, then I think we end up ignoring that directive, so it's fine.
I will look at how we can add additional tests to verify everything.
> 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
> Assignee: Gregory Chanan
> Fix For: 5.3, Trunk
>
> Attachments: SOLR-7734.patch, SOLR-7734.patch, 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
