Wrangler Service Pod Failing on CDAP 6.10.0 Kubernetes Deployment
40 views
Skip to first unread message
Bishwadeep Gupta
unread,
May 13, 2025, 1:32:57 AMMay 13
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to CDAP User
Hello Team, We are running a CDAP 6.10.0 cluster on Kubernetes and are currently trying to enable the Wrangler service on top of this setup. As we noticed that the CDAP Sandbox 6.10.0 distribution includes Wrangler version 4.10.0, we have added the Wrangler JARs into the artifacts folder of the app-fabric pod. The artifact addition and reload are reflected correctly in the CDAP UI, and the Wrangler service appears as expected. However, when we attempt to enable the Wrangler service from the UI, the Wrangler pod immediately transitions from the ‘init’ state to ‘terminated’, and is destroyed within 3 seconds. This makes it difficult for us to debug the root cause of the failure. We are seeing the attached logs in the app-fabric pod.
Has anyone encountered a similar issue or can provide guidance on how to troubleshoot and resolve this? Thanks in advance for your support.