Log files are stored as ${sys:druid.node.type}.log

[Subhashini2610]

I am using a k8s based deployment of Druid and see that each node creates log files that are named as
${sys:druid.node.type}.log

The variable is not getting resolved to the right node type. The log files are stored as ${sys:druid.node.type}.log or ${sys:druid.node.type}-<date>.log

Affected Version

Druid version: 28.0.0

Description

Due to the above problem, I am not able to index the logs appropriately. Am I missing something here?

[Subhashini2610]

Please help here

[abhishekagarwal87]

when you log into the pod, can you check the full command line that was used to start the druid process?

[Subhashini2610]

@abhishekagarwal87 How do I check that? The logs of the broker only contain the following:

2024-02-26T14:50:22+00:00 startup service broker
Setting druid.host=10.0.2.188 in /tmp/conf/druid/cluster/query/broker/runtime.properties
Setting druid.auth.authenticator.BasicMetadataAuthenticator.skipOnFailure=false in /tmp/conf/druid/cluster/query/broker/runtime.properties
Setting druid.broker.http.numThreads=15 in /tmp/conf/druid/cluster/query/broker/runtime.properties
Setting druid.indexer.logs.type=file in /tmp/conf/druid/cluster/query/broker/runtime.properties
Setting druid.emitter.statsd.port=8125 in /tmp/conf/druid/cluster/query/broker/runtime.properties
...
...
...

Also, the below is the broker container spec in my helm chart.

All other nodes also have similar spec, except the args, which refer to the particular node type like coordinator, historical etc.

[fectrain]

Hi, @Subhashini2610 , I met the similar issue.
Actually I'm using Helm-druid to manage the K8s deployment.
Usually the different services are deployed in different pods, So I'll just list out all pods(kubectl get pods -n <namespace>) and then ssh to the pod with specific pod_name, by this way I'm able to identify the which service/pod I'm accessing, even though the name of log_file looks like ${sys:druid.node.type}.log

[fectrain]

Hi, @Subhashini2610 @abhishekagarwal87 , the issue is probably due to druid.node.type not been specified when starting up, whose value is supposed to be the service type(e.g. broker/historical, etc..), have just made some fix right here