Description
This is a master issue to track things that we need to do to make cluster management easier.
- Introduce a new mode to disallow creation of collections by configuration and use the collection API instead
- New addReplica API to add a replica to a collection/shard
- New modifyCollection API to change replicationFactor, maxShardsPerNode configurations
- Update Solr Admin UI for the new APIs
- Longer term, optionally enforce the replicationFactor to add/remove nodes automatically
Some features have already been committed as part of other issues:
Attachments
Issue Links
- is related to
-
SOLR-6082 Umbrella JIRA for Admin UI and SolrCloud.
- Closed
- relates to
-
SOLR-7666 Umbrella ticket for Angular JS post-5.2.1 issues
- Closed
-
SOLR-5600 Don't perisist replicationFactor by default.
- Open
-
SOLR-5806 SolrCloud: UI link or script to remove node from clusterstate.json
- Open
-
SOLR-7716 misleading errors reported for CREATESHARD if new shard would exceed maxShardsPerNode
- Open
-
SOLR-5169 Provide a way to query for zookeeper quorum state and other cloud-related info
- Resolved
1.
|
Introduce autoManageReplicas collection property | Open | Unassigned | |
2.
|
Expose Overseer Status via JMX | Open | Unassigned |