[
https://issues.apache.org/jira/browse/OOZIE-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579232#comment-14579232
]
Robert Kanter commented on OOZIE-2187:
--------------------------------------
Hi [~nperiwal],
I just installed rbt and tried the above command (thanks, btw), but I get an
"HTTP 500" error. I added the {{--debug}} flag to get more detail, but it's
not super helpful:
{noformat}
>>> Got HTTP error: 500: <!DOCTYPE html>
<html>
<head>
<title>500 - Internal Server Error | Review Board</title>
</head>
<body>
<h1>Something broke! (Error 500)</h1>
<p>
It appears something broke when you tried to go to here. This is either
a bug in Review Board or a server configuration error. Please report
this to your administrator.
</p>
</body>
</title>
Traceback (most recent call last):
File "/usr/local/bin/rbt", line 9, in <module>
load_entry_point('RBTools==0.7.3.dev0', 'console_scripts', 'rbt')()
File "/Library/Python/2.6/site-packages/rbtools/commands/main.py", line 133,
in main
command.run_from_argv([RB_MAIN, command_name] + args)
File "/Library/Python/2.6/site-packages/rbtools/commands/__init__.py", line
612, in run_from_argv
exit_code = self.main(*args) or 0
File "/Library/Python/2.6/site-packages/rbtools/commands/post.py", line 745,
in main
(msg_prefix, e))
rbtools.commands.CommandError: Error validating diff
HTTP 500
{noformat}
Does this work for you?
> Add a way to specify a default JT/RM and NN
> -------------------------------------------
>
> Key: OOZIE-2187
> URL: https://issues.apache.org/jira/browse/OOZIE-2187
> Project: Oozie
> Issue Type: New Feature
> Components: core
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Attachments: OOZIE-2187.patch, OOZIE-2187.patch
>
>
> Oozie is cluster agnostic, which is why we require an RM/JT and NN per action
> in your workflow (or once via the <global> section). In practice, many users
> use one Oozie server per cluster, so it's an extra burden for them to have to
> specify this all the time. It would be convenient if we added configuration
> properties to oozie-site that would let you specify a default RM/JT and NN to
> use.
> This way, these users could completely omit the {{<job-tracker>}} and
> {{<name-node>}} fields from their workflows; as an added benefit, they can
> easily update these values if they ever rename/move their RM/JT or NN. We'd
> of course still allow specifying {{<job-tracker>}} and {{<name-node>}} in
> each action and {{<global>}} to allow individual workflows or actions to
> override the default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
