Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
This is the master issue for Cross Data Center Replication (CDCR)
described at a high level here: http://yonik.com/solr-cross-data-center-replication/
Attachments
Attachments
Issue Links
- contains
-
SOLR-6460 Keep transaction logs around longer
- Closed
-
SOLR-6461 peer cluster configuration
- Closed
-
SOLR-6462 forward updates asynchronously to peer clusters/leaders
- Closed
-
SOLR-6463 track update progress
- Closed
-
SOLR-6464 cross-cluster monitoring APIs
- Closed
- is depended upon by
-
SOLR-8263 Tlog replication could interfere with the replay of buffered updates
- Closed
- is related to
-
SOLR-8263 Tlog replication could interfere with the replay of buffered updates
- Closed
-
SOLR-6205 Make SolrCloud Data-center, rack or zone aware
- Resolved
- relates to
-
SOLR-8348 Decide whether to backport Cross Data Center Replication if we release Solr 5.5
- Resolved
-
SOLR-7807 Change CDCR tests to "Nightly" after they bake a bit.
- Closed
1.
|
Keep transaction logs around longer | Closed | Unassigned | |
2.
|
peer cluster configuration | Closed | Unassigned | |
3.
|
forward updates asynchronously to peer clusters/leaders | Closed | Unassigned | |
4.
|
track update progress | Closed | Unassigned | |
5.
|
cross-cluster monitoring APIs | Closed | Unassigned | |
6.
|
CDCR: fall back to whole-index replication when tlogs are insufficient | Closed | Shalin Shekhar Mangar | |
7.
|
easily create a peer cluster | Open | Unassigned | |
8.
|
Tlog replication could interfere with the replay of buffered updates | Closed | Erick Erickson |