Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.0
-
Component/s: cross-datacenter-replication, ns_server, RESTful-APIs
-
Security Level: Public
-
Labels:None
Description
We currently have separate and advertised call for creating replications.
But we rely on some already broken view to get replications with their status and we rely on explicit DELETE using couch-style call.
We need to do better.
We have tasks API that will provide us status potentially including error messages.
We need a way to list defined replications (perhaps tasks can do that too, why not, given replications are supposed to be always active). And we need a clear API to DELETE them.
But we rely on some already broken view to get replications with their status and we rely on explicit DELETE using couch-style call.
We need to do better.
We have tasks API that will provide us status potentially including error messages.
We need a way to list defined replications (perhaps tasks can do that too, why not, given replications are supposed to be always active). And we need a clear API to DELETE them.
MB-6381: expose xdcr replications via tasks API (Revision 7b1019eac277c03f8e25e30246eda0b8e96f8e55)MB-6381: implemented replication cancellation endpoint (Revision a6a856149e72ad3755d8f56aad5c61a800ee2839)Result = SUCCESS
Aliaksey Kandratsenka :
Files :
* src/ns_heart.erl
* src/ns_doctor.erl
* src/xdc_replication_sup.erl
Aliaksey Kandratsenka :
Files :
* src/xdc_rdoc_replication_srv.erl
* src/menelaus_web.erl