You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Deepak Barr (JIRA)" <ji...@apache.org> on 2016/01/25 17:57:39 UTC
[jira] [Created] (FALCON-1775) Incorrect error message on command
line
Deepak Barr created FALCON-1775:
-----------------------------------
Summary: Incorrect error message on command line
Key: FALCON-1775
URL: https://issues.apache.org/jira/browse/FALCON-1775
Project: Falcon
Issue Type: Improvement
Reporter: Deepak Barr
Assignee: Deepak Barr
Priority: Minor
I observed this behavior in case the falcon server fails to start properly ( say when MySQL is down in case of native schedular).
When I try to run a command, I get this -
bin/falcon entity -submit -type cluster -file examples/entity/filesystem/standalone-cluster.xml
ERROR: Bad Request;local/org.apache.falcon.FalconException::org.apache.falcon.FalconException: <html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
<title>Error 503 SERVICE_UNAVAILABLE</title>
</head>
<body>
<h2>HTTP ERROR: 503</h2>
<p>Problem accessing /secure/sync/submit/cluster. Reason:
<pre> SERVICE_UNAVAILABLE</pre></p>
<hr /><i><small>Powered by Jetty://</small></i>
At the top, the error says BAD REQUEST (HTTP 400; Client error) where as the real error should be Service Unavailable (HTTP 503; Server error).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)