[jira] [Updated] (FLUME-2801) Performance improvement on TailDir source
[
https://issues.apache.org/jira/browse/FLUME-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Seok Hong updated FLUME-2801:
-
Description:
This a proposal of performance improvement for new tailing source FLUME-2498.
Taildir source reads a file by 1byte, so the performance is very low compared
to tailing on exec source.
I tested lot's of ways to improve performance and implemented the best one.
Changes.
* Reading a file by a 8k block instead of 1 byte.
* Use byte[] for handling data instead of
ByteArrayDataOutput/ByteBuffer(direct)/.. for better performance.
* Don't convert byte[] to string and vice verse.
Simple file reading test results.
{quote}
File size: 100 MB,
Line size: 500 byte
Estimated time to read the file:
|Reading 1byte(Using the code in Taildir)|32544 ms|
|Reading 8K Block|431 ms|
{quote}
Testing on flume, it catches up the performance of tailing on exec source. (30x
performance boost)
was:
This a proposal of performance improvement for new tailing source FLUME-2498.
Taildir source reads a file by 1byte, so the performance is very low compared
to tailing on exec source.
I tested lot's of ways to improve performance and implemented the best one.
Changes.
* Reading a file by a 8k block instead of 1 byte.
* Use byte[] for handling data instead of
ByteArrayDataOutput/ByteBuffer(direct)/.. for better performance.
* Don't convert byte[] to string and vice verse.
On simple file reading test results.
{quote}
File size: 100 MB,
Line size: 500 byte
Estimated time to read the file:
|Reading 1byte(Using the code in Taildir)|32544 ms|
|Reading 8K Block|431 ms|
{quote}
Testing on flume, it catches up the performance of tailing on exec source. (30x
performance boost)
> Performance improvement on TailDir source
> -
>
> Key: FLUME-2801
> URL: https://issues.apache.org/jira/browse/FLUME-2801
> Project: Flume
> Issue Type: Improvement
> Components: Sinks+Sources
>Affects Versions: v1.7.0
>Reporter: Jun Seok Hong
> Fix For: v1.7.0
>
> Attachments: FLUME-2801.patch
>
>
> This a proposal of performance improvement for new tailing source FLUME-2498.
> Taildir source reads a file by 1byte, so the performance is very low compared
> to tailing on exec source.
> I tested lot's of ways to improve performance and implemented the best one.
> Changes.
> * Reading a file by a 8k block instead of 1 byte.
> * Use byte[] for handling data instead of
> ByteArrayDataOutput/ByteBuffer(direct)/.. for better performance.
> * Don't convert byte[] to string and vice verse.
> Simple file reading test results.
> {quote}
> File size: 100 MB,
> Line size: 500 byte
> Estimated time to read the file:
> |Reading 1byte(Using the code in Taildir)|32544 ms|
> |Reading 8K Block|431 ms|
> {quote}
> Testing on flume, it catches up the performance of tailing on exec source.
> (30x performance boost)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (FLUME-2498) Implement Taildir Source
[ https://issues.apache.org/jira/browse/FLUME-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905778#comment-14905778 ] Jun Seok Hong edited comment on FLUME-2498 at 9/24/15 3:54 AM: --- It was a mistake. I removed the file. was (Author: siefried12): It was a mistake. I removed it. > Implement Taildir Source > > > Key: FLUME-2498 > URL: https://issues.apache.org/jira/browse/FLUME-2498 > Project: Flume > Issue Type: New Feature > Components: Sinks+Sources >Reporter: Satoshi Iijima > Fix For: v1.7.0 > > Attachments: FLUME-2498-2.patch, FLUME-2498-3.patch, > FLUME-2498-4.patch, FLUME-2498-5.patch, FLUME-2498.patch > > > This is the proposal of implementing a new tailing source. > This source watches the specified files, and tails them in nearly real-time > once appends are detected to these files. > * This source is reliable and will not miss data even when the tailing files > rotate. > * It periodically writes the last read position of each file in a position > file using the JSON format. > * If Flume is stopped or down for some reason, it can restart tailing from > the position written on the existing position file. > * It can add event headers to each tailing file group. > A attached patch includes a config documentation of this. > This source requires Unix-style file system and Java 1.7 or later. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLUME-2498) Implement Taildir Source
[ https://issues.apache.org/jira/browse/FLUME-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905778#comment-14905778 ] Jun Seok Hong commented on FLUME-2498: -- It was a mistake. I removed it. > Implement Taildir Source > > > Key: FLUME-2498 > URL: https://issues.apache.org/jira/browse/FLUME-2498 > Project: Flume > Issue Type: New Feature > Components: Sinks+Sources >Reporter: Satoshi Iijima > Fix For: v1.7.0 > > Attachments: FLUME-2498-2.patch, FLUME-2498-3.patch, > FLUME-2498-4.patch, FLUME-2498-5.patch, FLUME-2498.patch > > > This is the proposal of implementing a new tailing source. > This source watches the specified files, and tails them in nearly real-time > once appends are detected to these files. > * This source is reliable and will not miss data even when the tailing files > rotate. > * It periodically writes the last read position of each file in a position > file using the JSON format. > * If Flume is stopped or down for some reason, it can restart tailing from > the position written on the existing position file. > * It can add event headers to each tailing file group. > A attached patch includes a config documentation of this. > This source requires Unix-style file system and Java 1.7 or later. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLUME-2801) Performance improvement on TailDir source
[
https://issues.apache.org/jira/browse/FLUME-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Seok Hong updated FLUME-2801:
-
Description:
This a proposal of performance improvement for new tailing source FLUME-2498.
Taildir source reads a file by 1byte, so the performance is very low compared
to tailing on exec source.
I tested lot's of ways to improve performance and implemented the best one.
Changes.
* Reading a file by a 8k block instead of 1 byte.
* Use byte[] for handling data instead of
ByteArrayDataOutput/ByteBuffer(direct)/.. for better performance.
* Don't convert byte[] to string and vice verse.
On simple file reading test results.
{quote}
File size: 100 MB,
Line size: 500 byte
Estimated time to read the file:
|Reading 1byte(Using the code in Taildir)|32544 ms|
|Reading 8K Block|431 ms|
{quote}
Testing on flume, it catches up the performance of tailing on exec source. (30x
performance boost)
was:
This a proposal of performance implementation for new tailing source FLUME-2498.
Taildir source reads a file by 1byte, so the performance is very low compared
to tailing on exec source.
I tested lot's of ways to improve performance and implemented the best one.
Changes.
* Reading a file by a 8k block instead of 1 byte.
* Use byte[] for handling data instead of
ByteArrayDataOutput/ByteBuffer(direct)/.. for better performance.
* Don't convert byte[] to string and vice verse.
On simple file reading test results.
{quote}
File size: 100 MB,
Line size: 500 byte
Estimated time to read the file:
|Reading 1byte(Using the code in Taildir)|32544 ms|
|Reading 8K Block|431 ms|
{quote}
Testing on flume, it catches up the performance of tailing on exec source. (30x
performance boost)
> Performance improvement on TailDir source
> -
>
> Key: FLUME-2801
> URL: https://issues.apache.org/jira/browse/FLUME-2801
> Project: Flume
> Issue Type: Improvement
> Components: Sinks+Sources
>Affects Versions: v1.7.0
>Reporter: Jun Seok Hong
> Fix For: v1.7.0
>
> Attachments: FLUME-2801.patch
>
>
> This a proposal of performance improvement for new tailing source FLUME-2498.
> Taildir source reads a file by 1byte, so the performance is very low compared
> to tailing on exec source.
> I tested lot's of ways to improve performance and implemented the best one.
> Changes.
> * Reading a file by a 8k block instead of 1 byte.
> * Use byte[] for handling data instead of
> ByteArrayDataOutput/ByteBuffer(direct)/.. for better performance.
> * Don't convert byte[] to string and vice verse.
> On simple file reading test results.
> {quote}
> File size: 100 MB,
> Line size: 500 byte
> Estimated time to read the file:
> |Reading 1byte(Using the code in Taildir)|32544 ms|
> |Reading 8K Block|431 ms|
> {quote}
> Testing on flume, it catches up the performance of tailing on exec source.
> (30x performance boost)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FLUME-2801) Performance improvement on TailDir source
[
https://issues.apache.org/jira/browse/FLUME-2801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Seok Hong updated FLUME-2801:
-
Attachment: FLUME-2801.patch
> Performance improvement on TailDir source
> -
>
> Key: FLUME-2801
> URL: https://issues.apache.org/jira/browse/FLUME-2801
> Project: Flume
> Issue Type: Improvement
> Components: Sinks+Sources
>Affects Versions: v1.7.0
>Reporter: Jun Seok Hong
> Fix For: v1.7.0
>
> Attachments: FLUME-2801.patch
>
>
> This a proposal of performance implementation for new tailing source
> FLUME-2498.
> Taildir source reads a file by 1byte, so the performance is very low compared
> to tailing on exec source.
> I tested lot's of ways to improve performance and implemented the best one.
> Changes.
> * Reading a file by a 8k block instead of 1 byte.
> * Use byte[] for handling data instead of
> ByteArrayDataOutput/ByteBuffer(direct)/.. for better performance.
> * Don't convert byte[] to string and vice verse.
> On simple file reading test results.
> {quote}
> File size: 100 MB,
> Line size: 500 byte
> Estimated time to read the file:
> |Reading 1byte(Using the code in Taildir)|32544 ms|
> |Reading 8K Block|431 ms|
> {quote}
> Testing on flume, it catches up the performance of tailing on exec source.
> (30x performance boost)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FLUME-2498) Implement Taildir Source
[ https://issues.apache.org/jira/browse/FLUME-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905676#comment-14905676 ] Hari Shreedharan commented on FLUME-2498: - This is already committed. Can you create a new jira and submit the patch there. > Implement Taildir Source > > > Key: FLUME-2498 > URL: https://issues.apache.org/jira/browse/FLUME-2498 > Project: Flume > Issue Type: New Feature > Components: Sinks+Sources >Reporter: Satoshi Iijima > Fix For: v1.7.0 > > Attachments: FLUME-2498-2.patch, FLUME-2498-3.patch, > FLUME-2498-4.patch, FLUME-2498-5.patch, FLUME-2498.patch > > > This is the proposal of implementing a new tailing source. > This source watches the specified files, and tails them in nearly real-time > once appends are detected to these files. > * This source is reliable and will not miss data even when the tailing files > rotate. > * It periodically writes the last read position of each file in a position > file using the JSON format. > * If Flume is stopped or down for some reason, it can restart tailing from > the position written on the existing position file. > * It can add event headers to each tailing file group. > A attached patch includes a config documentation of this. > This source requires Unix-style file system and Java 1.7 or later. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLUME-2498) Implement Taildir Source
[ https://issues.apache.org/jira/browse/FLUME-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Seok Hong updated FLUME-2498: - Attachment: FLUME-2801.patch > Implement Taildir Source > > > Key: FLUME-2498 > URL: https://issues.apache.org/jira/browse/FLUME-2498 > Project: Flume > Issue Type: New Feature > Components: Sinks+Sources >Reporter: Satoshi Iijima > Fix For: v1.7.0 > > Attachments: FLUME-2498-2.patch, FLUME-2498-3.patch, > FLUME-2498-4.patch, FLUME-2498-5.patch, FLUME-2498.patch > > > This is the proposal of implementing a new tailing source. > This source watches the specified files, and tails them in nearly real-time > once appends are detected to these files. > * This source is reliable and will not miss data even when the tailing files > rotate. > * It periodically writes the last read position of each file in a position > file using the JSON format. > * If Flume is stopped or down for some reason, it can restart tailing from > the position written on the existing position file. > * It can add event headers to each tailing file group. > A attached patch includes a config documentation of this. > This source requires Unix-style file system and Java 1.7 or later. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLUME-2498) Implement Taildir Source
[ https://issues.apache.org/jira/browse/FLUME-2498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Seok Hong updated FLUME-2498: - Attachment: (was: FLUME-2801.patch) > Implement Taildir Source > > > Key: FLUME-2498 > URL: https://issues.apache.org/jira/browse/FLUME-2498 > Project: Flume > Issue Type: New Feature > Components: Sinks+Sources >Reporter: Satoshi Iijima > Fix For: v1.7.0 > > Attachments: FLUME-2498-2.patch, FLUME-2498-3.patch, > FLUME-2498-4.patch, FLUME-2498-5.patch, FLUME-2498.patch > > > This is the proposal of implementing a new tailing source. > This source watches the specified files, and tails them in nearly real-time > once appends are detected to these files. > * This source is reliable and will not miss data even when the tailing files > rotate. > * It periodically writes the last read position of each file in a position > file using the JSON format. > * If Flume is stopped or down for some reason, it can restart tailing from > the position written on the existing position file. > * It can add event headers to each tailing file group. > A attached patch includes a config documentation of this. > This source requires Unix-style file system and Java 1.7 or later. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FLUME-2801) Performance improvement on TailDir source
Jun Seok Hong created FLUME-2801:
Summary: Performance improvement on TailDir source
Key: FLUME-2801
URL: https://issues.apache.org/jira/browse/FLUME-2801
Project: Flume
Issue Type: Improvement
Components: Sinks+Sources
Affects Versions: v1.7.0
Reporter: Jun Seok Hong
Fix For: v1.7.0
This a proposal of performance implementation for new tailing source FLUME-2498.
Taildir source reads a file by 1byte, so the performance is very low compared
to tailing on exec source.
I tested lot's of ways to improve performance and implemented the best one.
Changes.
* Reading a file by a 8k block instead of 1 byte.
* Use byte[] for handling data instead of
ByteArrayDataOutput/ByteBuffer(direct)/.. for better performance.
* Don't convert byte[] to string and vice verse.
On simple file reading test results.
{quote}
File size: 100 MB,
Line size: 500 byte
Estimated time to read the file:
|Reading 1byte(Using the code in Taildir)|32544 ms|
|Reading 8K Block|431 ms|
{quote}
Testing on flume, it catches up the performance of tailing on exec source. (30x
performance boost)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FLUME-2794) Flume 1.6 HBase 1.12 java.lang.NoSuchMethodError: org.apache.hadoop.hbase.client.Put.setWriteToWAL(Z)V
[ https://issues.apache.org/jira/browse/FLUME-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905673#comment-14905673 ] Hari Shreedharan commented on FLUME-2794: - I think we actually need to make code changes to remove the old methods and switch to the new ones. > Flume 1.6 HBase 1.12 java.lang.NoSuchMethodError: > org.apache.hadoop.hbase.client.Put.setWriteToWAL(Z)V > -- > > Key: FLUME-2794 > URL: https://issues.apache.org/jira/browse/FLUME-2794 > Project: Flume > Issue Type: Bug > Components: Sinks+Sources >Affects Versions: v1.6.0 >Reporter: Emmanuel Leroy > > with Hbase 1.1.2 and Flume 1.6 > getting this error: > ase_flume-9k2a4-1441998442358-ec273f9a-0-10152166], Starting > 2015-09-11 19:07:28,037 (SinkRunner-PollingRunner-DefaultSinkProcessor) > [ERROR - org.apache.flume.sink.hbase.HBaseSink.process(HBaseSink.java:351)] > Failed to commit transaction.Transaction rolled back. > java.lang.NoSuchMethodError: > org.apache.hadoop.hbase.client.Put.setWriteToWAL(Z)V > at org.apache.flume.sink.hbase.HBaseSink$3.run(HBaseSink.java:377) > at org.apache.flume.sink.hbase.HBaseSink$3.run(HBaseSink.java:372) > at > org.apache.flume.auth.SimpleAuthenticator.execute(SimpleAuthenticator.java:50) > at > org.apache.flume.sink.hbase.HBaseSink.putEventsAndCommit(HBaseSink.java:372) > at org.apache.flume.sink.hbase.HBaseSink.process(HBaseSink.java:342) > at > org.apache.flume.sink.DefaultSinkProcessor.process(DefaultSinkProcessor.java:68) > at org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLUME-2790) Flume Kafka NullPointerException while trying to connect to Kafka topic as source (consumer.ConsumerFetcherManager LeaderFinderThread Failed to find leader for Set)
[
https://issues.apache.org/jira/browse/FLUME-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hari Sekhon updated FLUME-2790:
---
Environment: HDP 2.3 fully kerberized including Kafka 0.8.2.2, using either
the HDP 2.3 version of Flume 1.5.2 or Apache Flume 1.6 downloaded from
apache.org (was: HDP 2.3 fully kerberized including Kafka 0.8.2.2 + Apache
Flume 1.6 downloaded from apache.org)
> Flume Kafka NullPointerException while trying to connect to Kafka topic as
> source (consumer.ConsumerFetcherManager LeaderFinderThread Failed to find
> leader for Set)
>
>
> Key: FLUME-2790
> URL: https://issues.apache.org/jira/browse/FLUME-2790
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
>Affects Versions: v1.6.0
> Environment: HDP 2.3 fully kerberized including Kafka 0.8.2.2, using
> either the HDP 2.3 version of Flume 1.5.2 or Apache Flume 1.6 downloaded from
> apache.org
>Reporter: Hari Sekhon
>Priority: Blocker
>
> I'm getting the following NullPointerException when trying to integrate Flume
> with Kafka as a source:
> {code}
> 15/09/10 14:39:25 INFO consumer.ZookeeperConsumerConnector:
> [flume_-1441895965442-55ac2e21], Cleared all relevant queues
> for this fetcher
> 15/09/10 14:39:25 INFO consumer.ZookeeperConsumerConnector:
> [flume_-1441895965442-55ac2e21], Cleared the data chunks in
> all the consumer message iterators
> 15/09/10 14:39:25 INFO consumer.ZookeeperConsumerConnector:
> [flume_-1441895965442-55ac2e21], Committing all offsets
> after clearing the fetcher queues
> 15/09/10 14:39:25 INFO consumer.ZookeeperConsumerConnector:
> [flume_-1441895965442-55ac2e21], Releasing partition
> ownership
> 15/09/10 14:39:25 INFO consumer.ZookeeperConsumerConnector:
> [flume_-1441895965442-55ac2e21], Consumer
> flume_-1441895965442-55ac2e21 rebalancing the following
> partitions: ArrayBuffer(0, 1) for topic with consumers:
> List(flume_-1441895965442-55ac2e21-0)
> 15/09/10 14:39:25 INFO consumer.ZookeeperConsumerConnector:
> [flume_-1441895965442-55ac2e21],
> flume_-1441895965442-55ac2e21-0 attempting to claim
> partition 0
> 15/09/10 14:39:25 INFO consumer.ZookeeperConsumerConnector:
> [flume_-1441895965442-55ac2e21],
> flume_-1441895965442-55ac2e21-0 attempting to claim
> partition 1
> 15/09/10 14:39:25 INFO consumer.ZookeeperConsumerConnector:
> [flume_-1441895965442-55ac2e21],
> flume_-1441895965442-55ac2e21-0 successfully owned partition
> 1 for topic
> 15/09/10 14:39:25 INFO consumer.ZookeeperConsumerConnector:
> [flume_-1441895965442-55ac2e21],
> flume_-1441895965442-55ac2e21-0 successfully owned partition
> 0 for topic
> 15/09/10 14:39:25 INFO consumer.ZookeeperConsumerConnector:
> [flume_-1441895965442-55ac2e21], Updating the cache
> 15/09/10 14:39:25 INFO consumer.ZookeeperConsumerConnector:
> [flume_-1441895965442-55ac2e21], Consumer
> flume_-1441895965442-55ac2e21 selected partitions :
> :0: fetched offset = -1: consumed offset =
> -1,:1: fetched offset = -1: consumed offset = -1
> 15/09/10 14:39:25 INFO consumer.ConsumerFetcherManager$LeaderFinderThread:
> [flume_-1441895965442-55ac2e21-leader-finder-thread],
> Starting
> 15/09/10 14:39:25 INFO consumer.ZookeeperConsumerConnector:
> [flume_-1441895965442-55ac2e21], end rebalancing consumer
> flume_-1441895965442-55ac2e21 try #0
> 15/09/10 14:39:25 INFO kafka.KafkaSource: Kafka source s1 started.
> 15/09/10 14:39:25 INFO instrumentation.MonitoredCounterGroup: Monitored
> counter group for type: SOURCE, name: s1: Successfully registered new MBean.
> 15/09/10 14:39:25 INFO instrumentation.MonitoredCounterGroup: Component type:
> SOURCE, name: s1 started
> 15/09/10 14:39:25 INFO utils.VerifiableProperties: Verifying properties
> 15/09/10 14:39:25 INFO utils.VerifiableProperties: Property client.id is
> overridden to flume
> 15/09/10 14:39:25 INFO utils.VerifiableProperties: Property
> metadata.broker.list is overridden to null:-1
> 15/09/10 14:39:25 INFO utils.VerifiableProperties: Property
> request.timeout.ms is overridden to 3
> 15/09/10 14:39:25 WARN consumer.ConsumerFetcherManager$LeaderFinderThread:
> [flume_-1441895965442-55ac2e21-leader-finder-thread], Failed
> to find leader for Set([,0], [,1])
> java.lang.NullPointerException
> at java.util.Hashtable.put(Hashtable.java:514)
> at
> kafka.producer.ProducerPool$.createSyncProducer(ProducerPool.scala:35)
> at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:50)
> at kafka.client.ClientUtils$.fetchTopicMetadata(ClientUtils.scala:88)
> at
> kafka.consumer.ConsumerFetcherManager$LeaderFinderThread.doWork(ConsumerFetcherManager.scala:66)
> at kaf
[jira] [Commented] (FLUME-2794) Flume 1.6 HBase 1.12 java.lang.NoSuchMethodError: org.apache.hadoop.hbase.client.Put.setWriteToWAL(Z)V
[ https://issues.apache.org/jira/browse/FLUME-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14904294#comment-14904294 ] Fred commented on FLUME-2794: - For your information, it works. Thanks > Flume 1.6 HBase 1.12 java.lang.NoSuchMethodError: > org.apache.hadoop.hbase.client.Put.setWriteToWAL(Z)V > -- > > Key: FLUME-2794 > URL: https://issues.apache.org/jira/browse/FLUME-2794 > Project: Flume > Issue Type: Bug > Components: Sinks+Sources >Affects Versions: v1.6.0 >Reporter: Emmanuel Leroy > > with Hbase 1.1.2 and Flume 1.6 > getting this error: > ase_flume-9k2a4-1441998442358-ec273f9a-0-10152166], Starting > 2015-09-11 19:07:28,037 (SinkRunner-PollingRunner-DefaultSinkProcessor) > [ERROR - org.apache.flume.sink.hbase.HBaseSink.process(HBaseSink.java:351)] > Failed to commit transaction.Transaction rolled back. > java.lang.NoSuchMethodError: > org.apache.hadoop.hbase.client.Put.setWriteToWAL(Z)V > at org.apache.flume.sink.hbase.HBaseSink$3.run(HBaseSink.java:377) > at org.apache.flume.sink.hbase.HBaseSink$3.run(HBaseSink.java:372) > at > org.apache.flume.auth.SimpleAuthenticator.execute(SimpleAuthenticator.java:50) > at > org.apache.flume.sink.hbase.HBaseSink.putEventsAndCommit(HBaseSink.java:372) > at org.apache.flume.sink.hbase.HBaseSink.process(HBaseSink.java:342) > at > org.apache.flume.sink.DefaultSinkProcessor.process(DefaultSinkProcessor.java:68) > at org.apache.flume.SinkRunner$PollingRunner.run(SinkRunner.java:147) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
