This message was deleted.
# troubleshootings
Slackbot
02/09/2023, 3:47 PMThis message was deleted.
a
Abhishek Agarwal
02/09/2023, 5:28 PMthat's what it looks like. one option is to build a custom druid docker image with those jars inside. And then use that docker image instead.
b
Ben Do
02/10/2023, 8:14 AMThanks! I thought using the init-conatiner should have the same effect as the jars are mounted in the folder before the actual druid pod is started. When add the new folder "protobuf-extensions" to plugin list (which according to the documentation you DONT have to do), you can even see the jars getting loaded - so they must be there or?
INFO [main] org.apache.druid.guice.ExtensionsLoader - Loading extension [protobuf-extensions], jars: kafka-protobuf-provider-6.0.1.jar, kotlin-stdlib-1.4.0.jar, wire-schema-3.2.2.jarBen Do
02/10/2023, 8:22 AMJust for reference if someone is trying something similar (despite me not having success yet) - this is the kustomize patch. The jars are downloaded in the init-script which is within a configmap:
Copy code
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: ignore
spec:
template:
spec:
initContainers:
- name: "druid-init"
image: "busybox:1.36.0"
command: ["sh", "-c", "sleep 10s;/scripts/init-script.sh"]
volumeMounts:
- mountPath: /scripts
name: init-script-volume
- mountPath: /protobuf-extensions
name: protobuf-extensions
containers:
- name: "druid"
volumeMounts:
- mountPath: /opt/druid/extensions/protobuf-extensions
name: protobuf-extensions
volumes:
- name: init-script-volume
configMap:
name: druid-init-script
defaultMode: 0755
- name: protobuf-extensions
emptyDir: {}a
Abhishek Agarwal
02/10/2023, 8:48 AMyeah. the jar is getting loaded. maybe it's a different problem. You can try to reproduce this locally without k8s.
b
Ben Do
02/10/2023, 11:58 AMI tried directly locally (via quickstart guide) and unfortunately I still had the same issues - so probably its not supposed to be.
5 Views