[
https://issues.apache.org/jira/browse/SOLR-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16284043#comment-16284043
]
Shawn Heisey commented on SOLR-3666:
------------------------------------
One of the first things that may require bikeshedding is where exactly to store
the sticky information for DIH in zookeeper, what exactly needs to be recorded,
and how it should be written. If it weren't for the fact that handler names
usually have forward slashes, I'd prefer znodes, but since I don't think znodes
can have that character, I'm betting that a json state file will be the right
way to go. Would URL encoding the handler name make sense, so we can use a
znode structure?
Looking at the Cloud->Tree info in Solr's admin UI, I notice that znodes have
timestamps, so I wonder if the "mtime" data could be used for expiration
purposes if we use pure znodes and something like URL encoding for the handler
name.
I will need to defer to others about the overseer, watches, and other such
details.
> DataImportHandler status command in SolrCloud does not work properly
> ---------------------------------------------------------------------
>
> Key: SOLR-3666
> URL: https://issues.apache.org/jira/browse/SOLR-3666
> Project: Solr
> Issue Type: Bug
> Components: contrib - DataImportHandler, SolrCloud
> Affects Versions: 4.0-ALPHA
> Reporter: Sauvik Sarkar
>
> The dataimport?command=status command does not work correctly when invoked on
> the node not running the DIH in a SolrCloud configuration.
> The expectation is that no matter which node is importing any other node
> should be able get the import status information.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
