4.6 KiB

Raw Blame History

layout
doc_page

Router Node

You should only ever need the router node if you have a Druid cluster well into the terabyte range. The router node can be used to route queries to different broker instances. By default, the broker routes queries based on how Rules are set up. For example, if 1 month of recent data is loaded into a hot cluster, queries that fall within the recent month can be routed to a dedicated set of brokers. Queries outside this range are routed to another set of brokers. This set up provides query isolation such that queries for more important data are not impacted by queries for less important data.

Running

io.druid.cli.Main server historical

Example Production Configuration

In this example, we have two tiers in our production cluster: hot and _default_tier. Queries for the hot tier are routed through the broker-hot set of brokers, and queries for the _default_tier are routed through the broker-cold set of brokers. If any exceptions or network problems occur, queries are routed to the broker-cold set of brokers. In our example, we are running with a c3.2xlarge EC2 node.

JVM settings:

-server
-server
-Xmx13g
-Xms13g
-XX:NewSize=256m
-XX:MaxNewSize=256m
-XX:+UseConcMarkSweepGC
-XX:+PrintGCDetails
-XX:+PrintGCTimeStamps
-XX:+UseLargePages
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/mnt/galaxy/deploy/current/
-Duser.timezone=UTC
-Dfile.encoding=UTF-8
-Djava.io.tmpdir=/mnt/tmp

-Dcom.sun.management.jmxremote.port=17071
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false

Runtime.properties:

druid.host=#{IP_ADDR}:8080
druid.port=8080
druid.service=druid/prod/router

druid.extensions.remoteRepositories=[]
druid.extensions.localRepository=lib
druid.extensions.coordinates=["io.druid.extensions:druid-histogram:0.6.156"]

druid.zk.service.host=#{ZK_IPs}
druid.zk.paths.base=/druid/prod

druid.discovery.curator.path=/prod/discovery

druid.processing.numThreads=1
druid.router.defaultBrokerServiceName=druid:prod:broker-cold
druid.router.coordinatorServiceName=druid:prod:coordinator
druid.router.tierToBrokerMap={"hot":"druid:prod:broker-hot","_default_tier":"druid:prod:broker-cold"}
druid.router.http.numConnections=50
druid.router.http.readTimeout=PT5M

druid.server.http.numThreads=100

druid.request.logging.type=emitter
druid.request.logging.feed=druid_requests

druid.monitoring.monitors=["com.metamx.metrics.SysMonitor","com.metamx.metrics.JvmMonitor"]

druid.emitter=http
druid.emitter.http.recipientBaseUrl=#{URL}

druid.curator.compress=true

Runtime Configuration

The router module uses several of the default modules in Configuration and has the following set of configurations as well:

Property	Possible Values	Description	Default
`druid.router.defaultBrokerServiceName`	Any string.	The default broker to connect to in case service discovery fails.	""
`druid.router.tierToBrokerMap`	An ordered JSON map of tiers to broker names. The priority of brokers is based on the ordering.	Queries for a certain tier of data are routed to their appropriate broker.	`highestPriority`
`druid.router.defaultRule`	Any string.	The default rule for all datasources.	"_default"
`druid.router.rulesEndpoint`	Any string.	The coordinator endpoint to extract rules from.	"/druid/coordinator/v1/rules"
`druid.router.coordinatorServiceName`	Any string.	The service discovery name of the coordinator.	null. Must be set.
`druid.router.pollPeriod`	Any ISO8601 duration.	How often to poll for new rules.	PT1M
`druid.router.strategies`	An ordered JSON array of objects.	All custom strategies to use for routing.	[{"type":"timeBoundary"},{"type":"priority"}]

Router Strategies

The router has a configurable list of strategies for how it select which broker to route queries to. The order of the strategies matter because as soon as something matches a condition, a broker is selected.

timeBoundary

{
  "type":"timeBoundary"
}

Including this strategy means all timeBoundary queries are always routed to the highest priority broker.

priority

{
  "type":"priority",
  "minPriority":0,
  "maxPriority":1
}

Queries with a priority set < minPriority are routed to the lowest priority broker. Queries with priority > maxPriority are routed to the highest priority broker. minPriority default is 0, maxPriority default is 1. Using default strategy values, if a query with priority 0 (the default) is sent, it skips the priority selection logic.

4.6 KiB Raw Blame History