https://linen.dev logo
Join Slack
Powered by
This message was deleted.
# troubleshooting
s
This message was deleted.
h
one more thing: is there a documented api endpoint to set the workerCategorySpec? The docs only mention doing it via UI, but I like to script it.
g
druid.server.tier
is more for segment assignment so I wouldn't expect that to stick here
druid.worker.category
OTOH I would expect to be honored… I see the same code in Indexer and MM for setting it from the props file
you'd use the select strategy type 
equalDistributionWithCategorySpec
(otherwise 
workerCategorySpec
is ignored)
h
Thanks Gian. I really miss a “default” tier for everything and then listing exceptions. And I tried both, the indexer stays in the 
_default_tier
. which is ok, as long as I could pin all 
index_kafka
to it and everything else to a default tier with a different name. Is there a comprehensive list of tasks, if I have to spell it out?
g
hmm do you have a "repro" for "Indexer stays in `_default_tier`"? like, some steps to follow on a fresh download that exhibit things not working as you'd expect?
I ask b/c I haven't tried personally but it seems like the code is there for it to work…
If it's a bug simplest thing is to just fix it
On your other question "Is there a comprehensive list of tasks" — not that I'm aware of in the docs, but I think you can get one from the Overlord itself by submitting a task with an invalid 
type
. IIRC it'll list out all the valid types in the error message
h
regarding reproducable:
Copy code
{% if item.tier is defined %}
          druid_server_tier={{ item.tier }}
          druid_worker_category={{ item.tier }}
          {% endif %}
I feed that into 
apache/druid:25.0.0
docker image. 
middleManger
and 
historical
respect it, indexer doesn't.
Copy code
$ curl -s -X POST druid-router.service.dw2.consul:8888/druid/indexer/v1/task -d'{"type":"reflection"' -H "Content-Type: application/json"|grep -o -E "\[.*?\]"|head -1|grep -o -E '\w+'|sort|jq --raw-input . | jq --slurp .
[
  "archive",
  "compact",
  "index",
  "index_hadoop",
  "index_kafka",
  "index_parallel",
  "index_realtime",
  "index_realtime_appenderator",
  "index_sub",
  "kill",
  "move",
  "noop",
  "partial_dimension_cardinality",
  "partial_dimension_distribution",
  "partial_index_generate",
  "partial_index_generic_merge",
  "partial_range_index_generate",
  "query_controller",
  "query_worker",
  "restore",
  "single_phase_sub_task"
]
maybe it's late, but you don't make it simple. How about an api call that just gives me this output?
follow up: looks like 
indexer
is observing category, but not showing in router overview.
g
maybe it's late, but you don't make it simple. How about an api call that just gives me this output?
ouch, I guess we deserve that 🙂 yeah, that'd be nice, as opposed to relying on an error message!
follow up: looks like indexer is observing category, but not showing in router overview.
ah, good to know! that probably means it isn't in 
sys.servers
(or it is but the UI isn't showing it)
Open in Slack
PreviousNext
Powered by