Home Forums Oozie Oozie to use MySQL instead of Derby

This topic contains 3 replies, has 4 voices, and was last updated by  Dave 5 months ago.

  • Creator
    Topic
  • #12273

    Hi,

    When I am doing the config change in oozie-site.xml to replace the Derby database with MySQL, the configurations are getting overridden with the original one. So, how can I use MySQL in place of Derby under Oozie.

    Also, we need to do the config change for providing the error code entry in the oozie-site.xml, e.g. the following property: oozie.service.LiteWorkflowStoreService.user.retry.error.code.ext

    Are these possible or not?

    Regards,
    –Vimlesh

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

  • Author
    Replies
  • #43912

    Dave
    Moderator

    Hi,

    Ambari will overwrite the changes made to the xml files directly.
    Any changes must be made in Ambari itself or you must use /var/lib/ambari-server/resources/scripts/configs.sh
    This enables a simpler way to use the Ambari API to change configurations.
    If you run
    “configs.sh get 127.0.0.1 CLUSTERNAME oozie-site”
    This will give you all the configurations which you can change, then you can find what you want to modify to MySQL and update them accordingly.

    Thanks

    Dave

    Collapse
    #32551

    York Yao
    Member

    Hi Vimlesh,

    Have you resolved this problem? I encountered the same problem. Can you share your solution?

    Hi Sef, I deployed the cluster using ambari.

    Thanks!

    York

    Collapse
    #12328

    Seth Lyubich
    Keymaster

    Hi Vimlesh,

    Can you please let me know which installation method you used to deploy your cluster?

    Thanks,
    Seth

    Collapse
Viewing 3 replies - 1 through 3 (of 3 total)