This section will help you troubleshoot problems related to the Dockerized Druid. 1 root root 7.4K Jan 18 20:39 zookeeper-stdout-supervisor-6AFVOR.log 1 root root 78 Jan 18 20:38 zookeeper-stderr-supervisor-Rm33j8.log 1 root root 153 Jan 18 20:38 mysql-stdout-supervisor-23izTf.log 1 root root 155 Jan 18 20:38 mysql-stderr-supervisor-NqN9nY.log 1 root root 28K Jan 18 21:14 druid-indexing-service-stdout-supervisor-5uyV7u.log 1 root root 7.9K Jan 18 21:09 druid-indexing-service-stderr-supervisor-x3YNlo.log 1 root root 18K Jan 18 20:39 druid-historical-stdout-supervisor-AJ0SZX.log 1 root root 0 Jan 18 20:38 druid-historical-stderr-supervisor-rmMHmF.log 1 root root 100K Jan 18 21:14 druid-coordinator-stdout-supervisor-Jq4WCi.log 1 root root 0 Jan 18 20:38 druid-coordinator-stderr-supervisor-RYMt5L.log 1 root root 18K Jan 18 20:39 druid-broker-stdout-supervisor-D28zOC.log 1 root root 0 Jan 18 20:38 druid-broker-stderr-supervisor-az6WwP.log This can be done by logging into the container using docker ps: AINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESĬbfc5612 druidio/example-cluster "/bin/sh -c 'export H" 7 seconds ago Up 6 seconds 2181/tcp, 2888/tcp, 3306/tcp, 3888/tcp, 8083/tcp, 0.0.0.0:3001->8081/tcp, 0.0.0.0:3000->8082/tcp sick_lamportĪnd attaching to the container using docker exec -ti 9e73cbfc5612 bash logs are written to /tmp/: ls -lah You might want to look into the logs when debugging the Druid processes. To build the docker image yourself clone access the coordinator console at Build Druid Docker Image.
Docker hyperkit using 2gb of memory download#
Wait a minute or so for Druid to start up and download the sample. README Druid Docker Image Run a simple Druid clusterĭownload and launch the docker image er pull druidio/example-clusterĮr run -rm -i -p 3000:8082 -p 3001:8081 druidio/example-cluster