HDFSEventSink begin is called when transaction opened due to other error
------------------------------------------------------------------------
Key: FLUME-1075
URL: https://issues.apache.org/jira/browse/FLUME-1075
Project: Flume
Issue Type: Bug
Components: Channel
Affects Versions: v1.1.0
Reporter: Brock Noland
If you HDFSEvenSink is unable to close a transaction, then the next time
process is called, begin is called on that same transaction and another error
is thrown.
{noformat}
2012-03-28 17:47:36,011 (SinkRunner-PollingRunner-DefaultSinkProcessor) [ERROR
- org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:165)] Unhandled
exception, logging and sleeping for 5000ms
java.lang.IllegalStateException: close() called when transaction is OPEN - you
must either commit or rollback first
at
com.google.common.base.Preconditions.checkState(Preconditions.java:172)
at
org.apache.flume.channel.BasicTransactionSemantics.close(BasicTransactionSemantics.java:179)
at
org.apache.flume.sink.hdfs.HDFSEventSink.process(HDFSEventSink.java:381)
at
org.apache.flume.sink.DefaultSinkProcessor.process(DefaultSinkProcessor.java:65)
at org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:148)
at java.lang.Thread.run(Thread.java:662)
2012-03-28 17:47:41,013 (SinkRunner-PollingRunner-DefaultSinkProcessor) [ERROR
- org.apache.flume.sink.hdfs.HDFSEventSink.process(HDFSEventSink.java:374)]
process failed
java.lang.IllegalStateException: begin() called when transaction is OPEN!
at
com.google.common.base.Preconditions.checkState(Preconditions.java:145)
at
org.apache.flume.channel.BasicTransactionSemantics.begin(BasicTransactionSemantics.java:131)
at
org.apache.flume.sink.hdfs.HDFSEventSink.process(HDFSEventSink.java:323)
at
org.apache.flume.sink.DefaultSinkProcessor.process(DefaultSinkProcessor.java:65)
at org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:148)
at java.lang.Thread.run(Thread.java:662)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
