4f221f9a12
* build(docker): refactor docker build scripts - add "build" option to docker-compose files to simplify rebuilding of images - create "start.sh" script so it's easier to override "command" in the quickstart's docker-compose file - use dockerize to wait for requisite services to start up - add a dedicated Dockerfile for kafka-setup This fixes https://github.com/linkedin/datahub/issues/1549 & https://github.com/linkedin/datahub/issues/1550
DataHub MetadataChangeEvent (MCE) Consumer Docker Image
Refer to DataHub MCE Consumer Job to have a quick understanding of the architecture and responsibility of this service for the DataHub.
Build & Run
cd docker/mce-consumer && docker-compose up --build
This command will rebuild the docker image and start a container based on the image.
To start a container using a previously built image, run the same command without the --build flag.
Container configuration
Docker Network
All Docker containers for DataHub are supposed to be on the same Docker network which is datahub_network.
If you change this, you will need to change this for all other Docker containers as well.
networks:
default:
name: datahub_network
Kafka and DataHub GMS Containers
Before starting datahub-mce-consumer container, datahub-gms and kafka containers should already be up and running.
These connections are configured via environment variables in docker-compose.yml:
environment:
- KAFKA_BOOTSTRAP_SERVER=broker:29092
- KAFKA_SCHEMAREGISTRY_URL=http://schema-registry:8081
The value of KAFKA_BOOTSTRAP_SERVER variable should be set to the host name of the kafka broker container within the Docker network.
The value of KAFKA_SCHEMAREGISTRY_URL variable should be set to the host name of the kafka schema registry container within the Docker network.
environment:
- GMS_HOST=datahub-gms
- GMS_PORT=8080
The value of GMS_HOST variable should be set to the host name of the datahub-gms container within the Docker network.