[jira] [Created] (FLUME-2550) Revamp Metrics reporting to use CodaHale Metrics package

Ashish Paliwal created FLUME-2550: - Summary: Revamp Metrics reporting to use CodaHale Metrics package Key: FLUME-2550 URL: https://issues.apache.org/jira/browse/FLUME-2550 Project: Flume Issu

Re: Using CodaHale metrics for monitoring

Makes sense. Thanks, Hari On Tue, Nov 11, 2014 at 9:51 PM, Ashish wrote: > That's what I had in mind, just need to figure out how to do it with > CodaHale. Want to avoid CodaHale MetricRegistry class floating around > in code. 1st step would be to migrate to CodaHale, I am yet to figure > out

Re: Using CodaHale metrics for monitoring

That's what I had in mind, just need to figure out how to do it with CodaHale. Want to avoid CodaHale MetricRegistry class floating around in code. 1st step would be to migrate to CodaHale, I am yet to figure out how managing the Reporter part. Let me try to put a patch together. On Wed, Nov 12, 2

[jira] [Comment Edited] (FLUME-2307) Remove Log writetimeout

[ https://issues.apache.org/jira/browse/FLUME-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14207651#comment-14207651 ] Hari Shreedharan edited comment on FLUME-2307 at 11/12/14 4:10 AM: -

[jira] [Commented] (FLUME-2307) Remove Log writetimeout

[ https://issues.apache.org/jira/browse/FLUME-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14207651#comment-14207651 ] Hari Shreedharan commented on FLUME-2307: - >From the logs you have here, I can't r

[jira] [Commented] (FLUME-2307) Remove Log writetimeout

[ https://issues.apache.org/jira/browse/FLUME-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14207648#comment-14207648 ] Nina Safonova commented on FLUME-2307: -- I didn't delete any files before I start to e

[jira] [Commented] (FLUME-2307) Remove Log writetimeout

[ https://issues.apache.org/jira/browse/FLUME-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14207645#comment-14207645 ] Hari Shreedharan commented on FLUME-2307: - >From your logs, I don't see the actual

Re: Using CodaHale metrics for monitoring

Currently the metrics exposed via Sources/sinks/channels are hardcoded. We could add a method to add custom metrics (I think it is already there in MonitoredCounterGroup, just not in the *Counter classes). Thanks, Hari On Tue, Nov 11, 2014 at 6:34 PM, Ashish wrote: > I was just playing aroun

[jira] [Commented] (FLUME-2307) Remove Log writetimeout

[ https://issues.apache.org/jira/browse/FLUME-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14207643#comment-14207643 ] Nina Safonova commented on FLUME-2307: -- I didn't try to delete checkpoint files. To k

[jira] [Commented] (FLUME-2307) Remove Log writetimeout

[ https://issues.apache.org/jira/browse/FLUME-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14207640#comment-14207640 ] Hari Shreedharan commented on FLUME-2307: - This does not seem like it is due to lo

[jira] [Commented] (FLUME-2307) Remove Log writetimeout

[ https://issues.apache.org/jira/browse/FLUME-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14207623#comment-14207623 ] Nina Safonova commented on FLUME-2307: -- OS is CentOS 6.5, flume version is 1.5 as I m

Re: Usage of CounterGroup class?

CounterGroup is obsolete (got it on another thread). Just closing this Thread to avoid Zombies :) On Sat, Nov 8, 2014 at 6:18 PM, Ashish wrote: > Hi, > > Can someone help me understand the usage of CounterGroup class. Can > see its usage for collecting metrics, but how is it reported (via > logg

Re: Using CodaHale metrics for monitoring

I was just playing around so piggy-backed it. The changes have to be within MonitoredCounterGroup and its sub-classes, as its used across the implementations. Let me raise a JIRA for this. One thing that I would like to have in future is to allow Sinks/Channels/Sources to be able to have custom co

Re: Review Request 18544: Hive Streaming sink

> On Aug. 21, 2014, 7:24 p.m., Brock Noland wrote: > > conf/log4j.properties, line 35 > > > > > > Hmm, are we doing this? had to put it in as there was just too much noise coming from the hive libraries during normal

[jira] [Updated] (FLUME-2549) Enable SSLv2Hello for HttpSource

[ https://issues.apache.org/jira/browse/FLUME-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Shreedharan updated FLUME-2549: Attachment: FLUME-2549.patch > Enable SSLv2Hello for HttpSource > --

[jira] [Updated] (FLUME-2548) Enable SSLv2Hello for Avro Source and NettyAvroRpcClient

[ https://issues.apache.org/jira/browse/FLUME-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Shreedharan updated FLUME-2548: Attachment: FLUME-2549.patch > Enable SSLv2Hello for Avro Source and NettyAvroRpcClient > --

[jira] [Updated] (FLUME-2548) Enable SSLv2Hello for Avro Source and NettyAvroRpcClient

[ https://issues.apache.org/jira/browse/FLUME-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Shreedharan updated FLUME-2548: Attachment: (was: FLUME-2549.patch) > Enable SSLv2Hello for Avro Source and NettyAvroRpc

[jira] [Updated] (FLUME-2548) Enable SSLv2Hello for Avro Source and NettyAvroRpcClient

[ https://issues.apache.org/jira/browse/FLUME-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Shreedharan updated FLUME-2548: Attachment: FLUME-2548.patch > Enable SSLv2Hello for Avro Source and NettyAvroRpcClient > --

[jira] [Created] (FLUME-2548) Enable SSLv2 for Avro Source and NettyAvroRpcClient

Hari Shreedharan created FLUME-2548: --- Summary: Enable SSLv2 for Avro Source and NettyAvroRpcClient Key: FLUME-2548 URL: https://issues.apache.org/jira/browse/FLUME-2548 Project: Flume Issue

[jira] [Created] (FLUME-2549) Enable SSLv2Hello for HttpSource

Hari Shreedharan created FLUME-2549: --- Summary: Enable SSLv2Hello for HttpSource Key: FLUME-2549 URL: https://issues.apache.org/jira/browse/FLUME-2549 Project: Flume Issue Type: Sub-task

[jira] [Updated] (FLUME-2547) Removing SSLv2Hello causes Java 6 clients to break

[ https://issues.apache.org/jira/browse/FLUME-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Shreedharan updated FLUME-2547: Attachment: (was: FLUME-2547.patch) > Removing SSLv2Hello causes Java 6 clients to break

[jira] [Updated] (FLUME-2548) Enable SSLv2Hello for Avro Source and NettyAvroRpcClient

[ https://issues.apache.org/jira/browse/FLUME-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Shreedharan updated FLUME-2548: Summary: Enable SSLv2Hello for Avro Source and NettyAvroRpcClient (was: Enable SSLv2 for Av

[jira] [Updated] (FLUME-2547) Removing SSLv2Hello causes Java 6 clients to break

[ https://issues.apache.org/jira/browse/FLUME-2547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Shreedharan updated FLUME-2547: Attachment: FLUME-2547.patch > Removing SSLv2Hello causes Java 6 clients to break >

[jira] [Commented] (FLUME-2546) HTTP Source docs should not that neither SSLv2Hello nor SSLv3 are supported

[ https://issues.apache.org/jira/browse/FLUME-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14207231#comment-14207231 ] Hari Shreedharan commented on FLUME-2546: - Holding off on this one till FLUME-2547

SSLv2Hello is required on Java 6

Hi, Right after we pushed 1.5.1 out (I have not even sent the announce email), we discovered that Java 6 requires SSLv2Hello on the server side for negotiation even if TLS is used (unless the client code is also changed to disable SSLv2Hello). So: - For HTTP Source, any clients running on Ja

[jira] [Created] (FLUME-2547) Removing SSLv2Hello causes Java 6 clients to break

Hari Shreedharan created FLUME-2547: --- Summary: Removing SSLv2Hello causes Java 6 clients to break Key: FLUME-2547 URL: https://issues.apache.org/jira/browse/FLUME-2547 Project: Flume Issue

[jira] [Updated] (FLUME-2546) HTTP Source docs should not that neither SSLv2Hello nor SSLv3 are supported

[ https://issues.apache.org/jira/browse/FLUME-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hari Shreedharan updated FLUME-2546: Attachment: FLUME-2546.patch I am applying this patch to the 1.5.1 docs and uploading to the

[jira] [Created] (FLUME-2546) HTTP Source docs should not that neither SSLv2Hello nor SSLv3 are supported

Hari Shreedharan created FLUME-2546: --- Summary: HTTP Source docs should not that neither SSLv2Hello nor SSLv3 are supported Key: FLUME-2546 URL: https://issues.apache.org/jira/browse/FLUME-2546 Proje

Re: [VOTE] Release Apache Flume 1.5.1 RC1

Thanks Hari for all the work. -roshan On Mon, Nov 10, 2014 at 10:55 PM, Hari Shreedharan < hshreedha...@cloudera.com> wrote: > This vote is now closed. > > > > > This vote has passed with 4 +1 binding votes: > > - Arvind Prabhakar > > - Roshan Naik > > - Hari Shreedharan > > - Jarcec > > > > > No

[jira] [Created] (FLUME-2545) How to convert *.bz2.tmp to *.bz2 file after restating the instance

Arun Gujjar created FLUME-2545: -- Summary: How to convert *.bz2.tmp to *.bz2 file after restating the instance Key: FLUME-2545 URL: https://issues.apache.org/jira/browse/FLUME-2545 Project: Flume

[jira] [Commented] (FLUME-2441) Unit test TestHTTPSource.java failed with IBM JDK 1.7

[ https://issues.apache.org/jira/browse/FLUME-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206932#comment-14206932 ] Hari Shreedharan commented on FLUME-2441: - It went into 1.5.1 > Unit test TestHTT

[jira] [Commented] (FLUME-2540) FLUME failed to rotate HDFS sink file from *.tmp to normal when timezone changed from PDT - PST on Nov 02, 2014

[ https://issues.apache.org/jira/browse/FLUME-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206928#comment-14206928 ] Arun Gujjar commented on FLUME-2540: Thanks Roshan, I thought of trying this option, w

Re: Using CodaHale metrics for monitoring

I think it is best to replace the current system rather than having multiple metrics systems. We should implement it such that it is transparent to user code, and the changes only go into MonitoredCounterGroup (the CounterGroup class is obsolete - dont bother). Thanks, Hari On Mon, Nov 10, 20

[jira] [Updated] (FLUME-2516) TestElasticSearchIndexRequestBuilderFactory fails with Locale != ENGLISH

[ https://issues.apache.org/jira/browse/FLUME-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santiago M. Mola updated FLUME-2516: Labels: easyfix easytest (was: ) > TestElasticSearchIndexRequestBuilderFactory fails with L

[jira] [Updated] (FLUME-2487) SyslogParser has rounding errors in timestamp parsing

[ https://issues.apache.org/jira/browse/FLUME-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santiago M. Mola updated FLUME-2487: Summary: SyslogParser has rounding errors in timestamp parsing (was: Timestamp mismatch in

[jira] [Updated] (FLUME-2487) Timestamp mismatch in TestMultiportSyslogTCPSource

[ https://issues.apache.org/jira/browse/FLUME-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santiago M. Mola updated FLUME-2487: Attachment: FLUME-2487-0.patch Patch updated with test case that may prove the bug. > Times

[jira] [Updated] (FLUME-2487) Timestamp mismatch in TestMultiportSyslogTCPSource

[ https://issues.apache.org/jira/browse/FLUME-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santiago M. Mola updated FLUME-2487: Attachment: (was: FLUME-2487-0.patch) > Timestamp mismatch in TestMultiportSyslogTCPSour

[jira] [Commented] (FLUME-2487) Timestamp mismatch in TestMultiportSyslogTCPSource

[ https://issues.apache.org/jira/browse/FLUME-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206507#comment-14206507 ] Santiago M. Mola commented on FLUME-2487: - [~ashishpaliwal] Given the non-determin

[jira] [Commented] (FLUME-2441) Unit test TestHTTPSource.java failed with IBM JDK 1.7

[ https://issues.apache.org/jira/browse/FLUME-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206393#comment-14206393 ] li xiang commented on FLUME-2441: - Hi Hari, this fix also goes into flume-1.5 ? > Unit te

Jenkins build is back to stable : Flume-trunk-hbase-98 #50

See

Jenkins build is still unstable: flume-trunk #693

See

[jira] [Commented] (FLUME-2385) Flume spans log file with "Spooling Directory Source runner has shutdown" messages at INFO level

[ https://issues.apache.org/jira/browse/FLUME-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206103#comment-14206103 ] Hudson commented on FLUME-2385: --- UNSTABLE: Integrated in flume-trunk #692 (See [https://bui

Jenkins build became unstable: flume-trunk #692

See