Adding example config files for indexer process. Also added status/selfDiscovered endpoint to indexer for self discovery#10679
Conversation
c15cc87 to
4c7416c
Compare
There was a problem hiding this comment.
the corresponding middleManager config has 4 tasks, should we match that for consistency?
There was a problem hiding this comment.
Sure! I can update it to match with MM config.
There was a problem hiding this comment.
given we have 1 processing thread per task in the example middle-manager config, I would set this to equal the worker capacity to have a comparable config.
There was a problem hiding this comment.
we probably need more heap to match our middle-manager config, which had 1GB per task.
There was a problem hiding this comment.
Made it 4g and also increased druid.processing.buffer.sizeBytes to 500MiB . Also increased -Xms and -Xmx setting to be 4x.
4c7416c to
6c53d8b
Compare
6c53d8b to
9a7d32d
Compare
9a7d32d to
a37824a
Compare
…lfDiscovered endpoint to indexer for self discovery of indexer.
a37824a to
062572a
Compare
xvrl
left a comment
There was a problem hiding this comment.
LGTM, cc @himanshug in case he has anything to add.
|
merging since test failures appear unrelated. |
…ndexer (apache#10679) Added the status/selfDiscovered endpoint to indexer. Per the api-reference doc, all services support status/selfDiscovered endpoint. So this change would fix that expected behavior. Also added example config files for indexer process that can be used to spin up the indexer process. (cherry picked from commit c2e26d2)
Add status/selfDiscovered endpoint to indexer for self discovery of indexer (apache#10679)
…ndexer (apache#10679) Added the status/selfDiscovered endpoint to indexer. Per the api-reference doc, all services support status/selfDiscovered endpoint. So this change would fix that expected behavior. Also added example config files for indexer process that can be used to spin up the indexer process.
…ndexer (apache#10679) Added the status/selfDiscovered endpoint to indexer. Per the api-reference doc, all services support status/selfDiscovered endpoint. So this change would fix that expected behavior. Also added example config files for indexer process that can be used to spin up the indexer process. (cherry picked from commit c2e26d2)
In this PR I have added example config files that can be used to spin up the indexer process. And have also added the
status/selfDiscoveredendpoint to indexer. Per the api-reference doc, all services supportstatus/selfDiscoveredendpoint. So this PR would fix that expected behavior.Code changes:
Since the SelfDiscovered endpoint is registered in the middle manager here, I followed the similar pattern in CliIndexer.java file as well
Testing
Built my own docker image, added the following in
docker-compose.ymlfileBrought all the services up
Made
status/selfDiscoveredcurl call to indexer running on port 8092 and got back 200 OK.