Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.apache.org
Date: Mon, 9 Mar 2015 16:14:38 +0000 (UTC)
From: "Adam Kawa (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12779450.1425490262000.38282.1425917678647@Atlassian.JIRA>
In-Reply-To: <JIRA.12779450.1425490262000@Atlassian.JIRA>
References: <JIRA.12779450.1425490262000@Atlassian.JIRA>
 <JIRA.12779450.1425490262502@arcas>
Subject: [jira] [Comment Edited] (FALCON-1068) When scheduling a process,
 Falcon throws "Bad Request;Could not commit transaction due to exception
 during persistence"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FALCON-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353154#comment-14353154 ] 

Adam Kawa edited comment on FALCON-1068 at 3/9/15 4:14 PM:
-----------------------------------------------------------

Before -submitAndSchedule I perform only delete. My scripts just wraps and parametrise 2 commands:

{code}
bin/falcon entity -type process -name <<name>> -delete
bin/falcon entity -submitAndSchedule -type process -file <<path>>
{code}


was (Author: kawaa):
Before -submitAndSchedule I perform only delete. My scripts just wraps and parametrise 2 commands:

{code]
bin/falcon entity -type process -name <<name>> -delete
bin/falcon entity -submitAndSchedule -type process -file <<path>>
{code}


> When scheduling a process, Falcon throws "Bad Request;Could not commit transaction due to exception during persistence"
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: FALCON-1068
>                 URL: https://issues.apache.org/jira/browse/FALCON-1068
>             Project: Falcon
>          Issue Type: Bug
>            Reporter: Adam Kawa
>         Attachments: falcon.application.log.FALCON-1068.rtf
>
>
> I have a simple script "manage-entity.sh process dss" that deletes, submit and schedules a Falcon process. 
> A couple of times per week, I get the "FalconCLIException: Bad Request;Could not commit transaction due to exception during persistence" when submitting the process. 
> The workaround is to restart Falcon server...
> e.g.:
> {code}
> $ ./manage-entity.sh process dss my-process.xml
> falcon/default/my-process(process) removed successfully (KILLED in ENGINE)
> Stacktrace:
> org.apache.falcon.client.FalconCLIException: Bad Request;Could not commit transaction due to exception during persistence
> 	at org.apache.falcon.client.FalconCLIException.fromReponse(FalconCLIException.java:44)
> 	at org.apache.falcon.client.FalconClient.checkIfSuccessful(FalconClient.java:1162)
> 	at org.apache.falcon.client.FalconClient.sendEntityRequestWithObject(FalconClient.java:684)
> 	at org.apache.falcon.client.FalconClient.submitAndSchedule(FalconClient.java:347)
> 	at org.apache.falcon.cli.FalconCLI.entityCommand(FalconCLI.java:371)
> 	at org.apache.falcon.cli.FalconCLI.run(FalconCLI.java:182)
> 	at org.apache.falcon.cli.FalconCLI.main(FalconCLI.java:132)
> $ ./falcon-restart.sh
> Hadoop is installed, adding hadoop classpath to falcon classpath
> Hadoop is installed, adding hadoop classpath to falcon classpath
> falcon started using hadoop version:  Hadoop 2.5.0
> $ ./manage-entity.sh process dss my-process.xml
> falcon/default/my-process(process) removed successfully (KILLED in ENGINE)
> schedule/default/my-process(process) scheduled successfully
> submit/falcon/default/Submit successful (process) my-process
> {code}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)