[
https://issues.apache.org/jira/browse/FALCON-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14349334#comment-14349334
]
Sowmya Ramesh edited comment on FALCON-1068 at 3/5/15 7:34 PM:
---------------------------------------------------------------
>From the log there is already read lock held when write is performed and
>LockTimeoutException occurs when trying to promote the lock. Are you
>performing any other operation before submitANdSchedule other than delete?
>From the code walk MetadataMappingService.onRemove doesn't have any
>implementation and hence no graph operation is done on deletion of entity.
>Also can you confirm if reties are being performed for this?
Form https://github.com/thinkaurelius/titan/wiki/Graph-Configuration: default
storage.lock-retries is set to 3 and storage.write-attempts to 5
{code}
Caused by: com.sleepycat.je.LockTimeoutException: (JE 5.0.73) Lock expired.
Locker 1719836551 9040_1915320434@qtp-1490009389-89 -
723ce874-0b88-4087-a742-3ae233e05df0_Txn: waited for lock on database=edgestore
LockAddr:864123167 LSN=0x3/0x4502f9 type=WRITE grant=WAIT_PROMOTION
timeoutMillis=500 startTime=1425489845022 endTime=1425489845523
Owners: [<LockInfo locker="1719836551 9040_1915320434@qtp-1490009389-89 -
723ce874-0b88-4087-a742-3ae233e05df0_Txn" type="READ"/>, <LockInfo
locker="1687215918 9031_344550172@qtp-1490009389-77_Txn" type="READ"/>]
Waiters: []
Transaction 1719836551 9040_1915320434@qtp-1490009389-89 -
723ce874-0b88-4087-a742-3ae233e05df0_Txn owns LockAddr:864123167 <LockInfo
locker="1719836551 9040_1915320434@qtp-1490009389-89 -
723ce874-0b88-4087-a742-3ae233e05df0_Txn" type="READ"/>
Transaction 1719836551 9040_1915320434@qtp-1490009389-89 -
723ce874-0b88-4087-a742-3ae233e05df0_Txn waits for LockAddr:864123167
{code}
was (Author: sowmyaramesh):
>From the log there is already read lock held when write is performed and
>LockTimeoutException occurs when trying to promote the lock. Are you
>performing any other operation before submitANdSchedule other than delete?
For the code walk MetadataMappingService.onRemove doesn't have any
implementation and hence no graph operation is done on deletion of entity. Also
can you confirm is reties are performed for this?
Form https://github.com/thinkaurelius/titan/wiki/Graph-Configuration: default
storage.lock-retries is set to 3 and storage.write-attempts to 5
{code}
Caused by: com.sleepycat.je.LockTimeoutException: (JE 5.0.73) Lock expired.
Locker 1719836551 9040_1915320434@qtp-1490009389-89 -
723ce874-0b88-4087-a742-3ae233e05df0_Txn: waited for lock on database=edgestore
LockAddr:864123167 LSN=0x3/0x4502f9 type=WRITE grant=WAIT_PROMOTION
timeoutMillis=500 startTime=1425489845022 endTime=1425489845523
Owners: [<LockInfo locker="1719836551 9040_1915320434@qtp-1490009389-89 -
723ce874-0b88-4087-a742-3ae233e05df0_Txn" type="READ"/>, <LockInfo
locker="1687215918 9031_344550172@qtp-1490009389-77_Txn" type="READ"/>]
Waiters: []
Transaction 1719836551 9040_1915320434@qtp-1490009389-89 -
723ce874-0b88-4087-a742-3ae233e05df0_Txn owns LockAddr:864123167 <LockInfo
locker="1719836551 9040_1915320434@qtp-1490009389-89 -
723ce874-0b88-4087-a742-3ae233e05df0_Txn" type="READ"/>
Transaction 1719836551 9040_1915320434@qtp-1490009389-89 -
723ce874-0b88-4087-a742-3ae233e05df0_Txn waits for LockAddr:864123167
{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)
