[
https://issues.apache.org/jira/browse/OOZIE-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845861#comment-13845861
]
Robert Kanter commented on OOZIE-1609:
--------------------------------------
Would that be for unit tests or for manually testing it in a deployment?
For manually testing it, I suppose OOZIE-1616 would be helpful :) Otherwise,
you can just delete the jars from the old sharelib. Then, if you run something
like a pig action, if it gives a {{ClassNotFoundException}}, then its using the
old sharelib and didn't work; if it works, then its using the new sharelib.
For unit tests, this could be a little tricky. I'd say there's two things you
need to test, and its probably easier to do them separately.
# That Oozie sends the correct request to the other servers when you do the
update command.
#- You can do something similar to how I tested the log streaming in
{{TestZKXLogStreamingService#testStreamingWithMultipleOozieServers}}.
Basically, I created a "dummy" servlet and used the {{DummyZKOozie}} from
{{ZKXTestCase}} to say that there's another Oozie server running at the
servlet's address. And in the servlet, I had a way of checking that it
received the right request from the real Oozie (The dummy servlet I used also
returned some logs to the real Oozie, but I don't think you need to do anything
like that for your test)
# That Oozie receives and properly handles the request to do the update command.
#- This is easier to test, and you probably don't need anything beyond what
tests you had in OOZIE-1519.
Makes sense?
> HA support for share lib.
> -------------------------
>
> Key: OOZIE-1609
> URL: https://issues.apache.org/jira/browse/OOZIE-1609
> Project: Oozie
> Issue Type: Sub-task
> Components: HA
> Reporter: purshotam shah
> Assignee: purshotam shah
>
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
