[
https://issues.apache.org/jira/browse/SOLR-2765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125232#comment-13125232
]
Mark Miller commented on SOLR-2765:
-----------------------------------
One thing we probably want to consider are the limitations we might hit as this
XML file grows. EG - at some point, is grabbing a 800k file on every update
going to be a lot worse than incremental updates against zknodes? Are we going
to be okay with a max limit of nodes in the low 1000's? (Zk max file size is 1
MB - is that overridable without hacking a version?). We will likely add more
meta data to each node over time.
Also, should we consider JSON or YAML over XML? Solr has historically used XML
for config, but I don't want that to unduly influence the right choice here.
Solr also has JSON support (which I would like as better default for talking to
Solr myself).
> Shard/Node states
> -----------------
>
> Key: SOLR-2765
> URL: https://issues.apache.org/jira/browse/SOLR-2765
> Project: Solr
> Issue Type: Sub-task
> Components: SolrCloud, update
> Reporter: Yonik Seeley
> Fix For: 4.0
>
> Attachments: cluster_state-file.patch, combined.patch,
> incremental_update.patch, scheduled_executors.patch, shard-roles.patch,
> solrcloud.patch
>
>
> Need state for shards that indicate they are recovering, active/enabled, or
> disabled.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
