The load data of Druid is divided into two categories: bulk load (historical data) and real-time load (new data), this article describes the bulk load data
Indexing Service
The bulk load data needs to use the Indexing Service, which is a stand-alone service that accepts tasks in the form of a POST request. The output of the most tasks is segments.
Running the Overlord node
Start command
Java-xmx2g-duser.timezone=utc-dfile.encoding=utf-8-classpath Lib/*:config/overlord io.druid.cli.Main Server Overlord
Configuration file
Druid.host=localhost
druid.port=8087
Druid.service=overlord
Druid.zk.service.host=localhost
druid.extensions.coordinates=["io.druid.extensions:druid-kafka-seven:0.6.143"]
Druid.db.connector.connecturi=jdbc:mysql://localhost:3306/druid
Druid.db.connector.user=druid
Druid.db.connector.password=diurd
Druid.selectors.indexing.servicename=overlord
druid.indexer.queue.startdelay=pt0m
Druid.indexer.runner.javaopts= "-server-xmx256m"
Druid.indexer.fork.property.druid.processing.numthreads=1
druid.indexer.fork.property.druid.computation.buffer.size=100000000
Load Data 1