I tried to kill a oozie coordinator job like this:
$ oozie job -oozie http://10.0.3.2:11000/oozie -kill 0003288-130913181709024-oozie-oozi-C
There is no any error appears.
But after I check the oozie UI, the job still exists.
I encounter this error sometimes on my testing environment, where Oozie uses Derby as database. The solution is to clean Oozie state by removing the database:
sudo /etc/init.d/oozie stop
sudo rm -rf /var/lib/oozie/oozie-db/
sudo /etc/init.d/oozie start
Of course, this solution may not be appropriate for production system (althrough I've never seen this error in production).
本文介绍了一种在Oozie使用Derby作为数据库的测试环境中遇到的作业无法正常删除的情况及其解决方案。该方案涉及停止Oozie服务、清除数据库文件并重启服务等步骤。需要注意的是,此方法可能不适合生产环境。
1412

被折叠的 条评论
为什么被折叠?



