I am noticing that the “Undeploy” button for Eventing function does not always work. Is the NQ1L command that I can stop any processes in Eventing function and undeploy it? So far I would leave Eventing function “be” for 20-30 min, and then would be able to undeploy function with the button, but for the last 2 days I complete was unable to undeploy the eventing function.
Hi @evgeniya.bell There is no n1ql command to stop eventing function undeploy. Ideally, it should not take long to undeploy a function. Could you please share below details to help root cause the problem?
I can help further after looking at the logs. Alternatively, we can share a tool that resets all eventing definitions if you’d like to start over. If you need this tool, please let us know.
@PrashantSingh - if you’re using Couchbase 6.0.x or 6.5.x - the tool “cbevent” comes with the installed product as “/opt/couchbase/bin/cbevent”. You can run “cbevent -flush” to remove all handlers and reset (note that handlers will be lost if flushed). Please let me know if it helps. If you’re on an older version which doesn’t come with this tool, please let me know your OS and Couchbase Version and I can share a backport of the tool.
If flushing the handlers is not an option, please let me know and I can dig in to see why it’s not undeploying and how we can remove whatever is blocking the undeploy.