Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

...

REMOVED IN RELEASE G - NO LONGER SUPPORTED

MirrorMaker is a stand-alone tool for copying data between two Apache Kafka clusters. It is a Kafka consumer and producer hooked together. Data is read from topics in the origin cluster and written to a topic with the same name in the destination cluster. You can run many such mirroring processes to increase throughput and for fault-tolerance

DMaaP Message Router offers the following REST API to create a mirror maker process, update a mirror maker process etc.  


Mirror Maker


Expand
titleCreate Mirror Maker

POST /mirrormakers/create

This API will create a Mirror Maker.

Required AAF Permissions : org.onap.dmaap.mr.mirrormaker|*|admin

Request Payload:

Parameter NameReq'd

Description


createMirrorMakerYMirror Maker Request Object
nameYUnique Name for the MirrorMaker A-Z 1-0 only
consumerYConsumer hostname/IP Address 
producerYProducer hostname/IP Address
numStreamsOptionalNumber of consumer threads to start. (If not provided default is 1)
whitelistOptionalTopic names to be whitelisted. This can be provided later using createWhitelist API
enablelogCheckOptional


Enable error log monitoring on the MirrorMaker thread. Default values is False.

If not provided error log is not monitored.


{
"createMirrorMaker":
{
"name": "centraltoedge",
"consumer": "10.12.6.98:30491",
"producer": "10.12.5.108:30491",
"numStreams": "3",
"whitelist": "org.onap.dmaap.mr.mrtesttopic",
"enablelogCheck": "true"
}
}


Response Payload:

{
"listMirrorMaker": {
"name": "centraltoedge",
"producer": "10.12.5.108:30491",
"whitelist": "org.onap.dmaap.mr.mrtesttopic",
"enablelogCheck": true,
"consumer": "10.12.6.98:30491",
"status": "RESTARTING",
"numStreams": 3
}
}


Error Messages:

Error ResonError Message
No AAF Mirror Maker Admin permissionNo Mirror Maker Admin permission.
Creating new MirrorMaker with existing MirrroMaker nameMirrorMaker <MM Name> already exists
Incorrect payloadThis is not a CreateMirrorMaker request. Please try again.
Consumer field/value missingPlease provide Consumer host:port details
Producer field/value missingPlease provide Producer host:port details
Incorrect naming conventionMirror Maker name can only contain alpha numeric
Incorrect JSONIncorrect JSON object.Incorrect JSON object.Could not parse JSON. Please correct the JSON format and try again.
If Mirror Maker agent is down or it takes more than (right now it is configured 15 seconds)listMirrorMaker is not available, please make sure MirrorMakerAgent is running


...

Expand
titleDelete Whitelist

POST /mirrormakers/deletewhitelist

This API removes a topic from whitelist.

AAF permissions required: org.onap.dmaap.mr.mirrormaker|*|user , org.onap.dmaap.mr.topicFactory|:org.onap.dmaap.mr.topic:org.onap.dmaap.mr|create

Request Payload:

Parameter NameReq'dDescription
nameYMirror Maker name
namespaceYa namespace
whitelistTopicNameYa topic name that contains only alpha numeric value


{
"name":"centraltoedge",
"namespace":"org.onap.dmaap.mr",
"whitelistTopicName":"org.onap.dmaap.mr.mrtesttopic2"
}

Response Payload:

{
"listMirrorMaker": [
{
"name": "centraltoedge",
"producer": "10.12.5.108:30491",
"whitelist": "org.onap.dmaap.mr.mrtesttopic",
"enablelogCheck": true,
"consumer": "10.12.6.98:30491",
"status": "RESTARTING",
"numStreams": 3
}
],
}


Error Messages:

Error ReasonError Message
No AAF Mirror Maker User permissionNo Mirror Maker User permission.
No AAF Mirror Maker User Create permissionNo Mirror Maker User Create permission.
Incorrect JSONIncorrect JSON object.Could not parse JSON. Please correct the JSON format and try again.
Request contain topic does not existThe topic does not exist.
If Mirror Maker agent is down or it takes more than (right now it is configured 15 second)listWhiteList is not available, please make sure MirrorMakerAgent is running
Incorrect payloadThis is not a DeleteAllWhitelist request. Please try again.



Recommendations:

1) Topic partitions must be same in both producer and consumer Kafka clusters

2) For better performance numStreams should match  to the topic  partitions