Indexer

I have two middle manager running as remote indexer . I can see only one is getting all the request other one is remaining idle .

I have check ZK entry for indexer announcement and it has both the node entry . By any chance I’m missing anything here ??

Have you changed your middle manager selectStrategy? It defaults to fillCapacity but it sounds like you’re looking for equalDistribution. http://druid.io/docs/0.8.3/configuration/indexing-service.html

Michael

Here is my overlord runtime , I m running indexer as remote

-----overlord runtime

Default host: localhost. Default port: 8090. If you run each node type on its own node in production, you should override these values to be IP:8080

druid.host=

druid.port=8080

druid.service=overlord

Run the overlord in local mode with a single peon to execute tasks

This is not recommended for production.

#druid.indexer.queue.startDelay=PT0M

This setting is too small for real production workloads

#druid.indexer.runner.javaOpts=-server -Xmx256m

These settings are also too small for real production workloads

Please see our recommended production settings in the docs (http://druid.io/docs/latest/Production-Cluster-Configuration.html)

#druid.indexer.fork.property.druid.processing.numThreads=1

#druid.indexer.fork.property.druid.computation.buffer.size=100000000

Uncomment following property if you are running Middle Manager

druid.indexer.runner.type=remote

druid.indexer.storage.type=metadata

druid.indexer.logs.type=s3

druid.indexer.logs.s3Bucket=

druid.indexer.logs.s3Prefix=log/v1

druid.indexer.runner.type=remote

selectStrategy=equalDistribution

-----middlemanager runtime

druid.host=

druid.port=8080

druid.service=middlemanager

Store task logs in deep storage

druid.indexer.logs.type=s3

druid.indexer.logs.s3Bucket=druid-dev-test

druid.indexer.logs.s3Prefix=log/v1

Resources for peons

druid.indexer.runner.javaOpts=-server -Xmx3g -XX:+UseG1GC -XX:MaxGCPauseMillis=100 -XX:+PrintGCDetails -XX:+PrintGCTimeStamps

druid.indexer.task.baseTaskDir=/mnt/persistent/task/

Peon properties

#druid.indexer.fork.property.druid.monitoring.monitors=[“com.metamx.metrics.JvmMonitor”]

druid.indexer.fork.property.druid.processing.buffer.sizeBytes=53687912

druid.indexer.fork.property.druid.processing.numThreads=2

druid.indexer.fork.property.druid.segmentCache.locations=[{“path”: “/mnt/persistent/zk_druid”, “maxSize”: 0}]

druid.indexer.fork.property.druid.server.http.numThreads=25

druid.indexer.fork.property.druid.storage.archiveBaseKey=_archive

druid.indexer.fork.property.druid.storage.archiveBucket=druid-dev-test

druid.indexer.fork.property.druid.storage.baseKey=archive/v1

druid.indexer.fork.property.druid.storage.bucket=druid-dev-test

druid.indexer.fork.property.druid.storage.type=s3

druid.worker.capacity=2

druid.worker.ip=0.0.0.0

-----ZK entry …

[zk: localhost:2181(CONNECTED) 4] ls /druid/indexer/announcements

[:8080,:8080]

selectStrategy is actually set dynamically via post to the overlord. I don’t believe there is a way to set them in the configs. The doc page has a bunch more information in Dynamic Configuration section.

Michael