[jira] [Created] (FLUME-2832) Caught exception during HTTP server start

2015-10-30 Thread Harikrishna (JIRA) 
Harikrishna created FLUME-2832:
--

 Summary: Caught exception during HTTP server start
 Key: FLUME-2832
 URL: https://issues.apache.org/jira/browse/FLUME-2832
 Project: Flume
  Issue Type: Bug
  Components: Node
Affects Versions: v0.9.4
 Environment:  'flume-node-0.9.4' on Windows 8 (Node 1)
and another in cent os 6.5 (node 2)
Reporter: Harikrishna


I have installed 'flume-node-0.9.4' on Windows 8 (Node 1)
and another in cent os 6.5 (node 2)
i have to pull the data from windows to linux using flume agent from windows

my windows log files in E:/success/logs

so i'm not enable to localhost on 35872 in windows agent.
15/10/30 11:25:58 WARN util.InternalHttpServer: Caught exception during HTTP 
server start.
java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
at 
org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:216)
at 
org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:315)
at 
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.Server.doStart(Server.java:235)
at 
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at 
com.cloudera.util.InternalHttpServer.start(InternalHttpServer.java:188)
at com.cloudera.flume.agent.FlumeNode.start(FlumeNode.java:275)
at 
com.cloudera.flume.agent.FlumeNodeDaemon.start(FlumeNodeDaemon.java:86)
at 
com.cloudera.flume.agent.FlumeNodeDaemon.windowsService(FlumeNodeDaemon.java:54)
15/10/30 11:25:58 ERROR agent.FlumeNode: Unexpected exception/error thrown! 
Unable to start HTTP server
com.cloudera.util.InternalHttpServer$InternalHttpServerException: Unable to 
start HTTP server
at 
com.cloudera.util.InternalHttpServer.start(InternalHttpServer.java:194)
at com.cloudera.flume.agent.FlumeNode.start(FlumeNode.java:275)
at 
com.cloudera.flume.agent.FlumeNodeDaemon.start(FlumeNodeDaemon.java:86)
at 
com.cloudera.flume.agent.FlumeNodeDaemon.windowsService(FlumeNodeDaemon.java:54)
Caused by: java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.Net.bind(Unknown Source)
at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
at 
org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:216)
at 
org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:315)
at 
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.Server.doStart(Server.java:235)
at 
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at 
com.cloudera.util.InternalHttpServer.start(InternalHttpServer.java:188)
... 3 more
15/10/30 11:25:58 INFO agent.MultiMasterRPC: 
15/10/30 11:25:58 INFO agent.AvroMasterRPC: Connected to master at 
localhost:35872
15/10/30 11:26:02 INFO agent.MultiMasterRPC: 
15/10/30 11:26:02 INFO agent.AvroMasterRPC: Connected to master at 
localhost:35872
15/10/30 11:26:03 INFO agent.MultiMasterRPC: 
15/10/30 11:26:03 INFO agent.AvroMasterRPC: Connected to master at 
localhost:35872



please kindly suggest me.




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

[jira] [Commented] (FLUME-2832) Caught exception during HTTP server start

2015-10-30 Thread Gonzalo Herreros (JIRA) 

[ 
https://issues.apache.org/jira/browse/FLUME-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14982119#comment-14982119
 ] 

Gonzalo Herreros commented on FLUME-2832:
-

java.net.BindException: Address already in use: bind
It might not be obvious because it speaks of "address" but it means the port is 
taken. It's possible to bind the port to a different address but normally you 
don't want that.
Use a different port or find which process is taking it.

I would also advice you to upgrade to a modern version of Flume


> Caught exception during HTTP server start
> -
>
> Key: FLUME-2832
> URL: https://issues.apache.org/jira/browse/FLUME-2832
> Project: Flume
>  Issue Type: Bug
>  Components: Node
>Affects Versions: v0.9.4
> Environment:  'flume-node-0.9.4' on Windows 8 (Node 1)
> and another in cent os 6.5 (node 2)
>Reporter: Harikrishna
>
> I have installed 'flume-node-0.9.4' on Windows 8 (Node 1)
> and another in cent os 6.5 (node 2)
> i have to pull the data from windows to linux using flume agent from windows
> my windows log files in E:/success/logs
> so i'm not enable to localhost on 35872 in windows agent.
> 15/10/30 11:25:58 WARN util.InternalHttpServer: Caught exception during HTTP 
> server start.
> java.net.BindException: Address already in use: bind
>   at sun.nio.ch.Net.bind0(Native Method)
>   at sun.nio.ch.Net.bind(Unknown Source)
>   at sun.nio.ch.Net.bind(Unknown Source)
>   at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
>   at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
>   at 
> org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:216)
>   at 
> org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:315)
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>   at org.mortbay.jetty.Server.doStart(Server.java:235)
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>   at 
> com.cloudera.util.InternalHttpServer.start(InternalHttpServer.java:188)
>   at com.cloudera.flume.agent.FlumeNode.start(FlumeNode.java:275)
>   at 
> com.cloudera.flume.agent.FlumeNodeDaemon.start(FlumeNodeDaemon.java:86)
>   at 
> com.cloudera.flume.agent.FlumeNodeDaemon.windowsService(FlumeNodeDaemon.java:54)
> 15/10/30 11:25:58 ERROR agent.FlumeNode: Unexpected exception/error thrown! 
> Unable to start HTTP server
> com.cloudera.util.InternalHttpServer$InternalHttpServerException: Unable to 
> start HTTP server
>   at 
> com.cloudera.util.InternalHttpServer.start(InternalHttpServer.java:194)
>   at com.cloudera.flume.agent.FlumeNode.start(FlumeNode.java:275)
>   at 
> com.cloudera.flume.agent.FlumeNodeDaemon.start(FlumeNodeDaemon.java:86)
>   at 
> com.cloudera.flume.agent.FlumeNodeDaemon.windowsService(FlumeNodeDaemon.java:54)
> Caused by: java.net.BindException: Address already in use: bind
>   at sun.nio.ch.Net.bind0(Native Method)
>   at sun.nio.ch.Net.bind(Unknown Source)
>   at sun.nio.ch.Net.bind(Unknown Source)
>   at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
>   at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
>   at 
> org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:216)
>   at 
> org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:315)
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>   at org.mortbay.jetty.Server.doStart(Server.java:235)
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>   at 
> com.cloudera.util.InternalHttpServer.start(InternalHttpServer.java:188)
>   ... 3 more
> 15/10/30 11:25:58 INFO agent.MultiMasterRPC: 
> 15/10/30 11:25:58 INFO agent.AvroMasterRPC: Connected to master at 
> localhost:35872
> 15/10/30 11:26:02 INFO agent.MultiMasterRPC: 
> 15/10/30 11:26:02 INFO agent.AvroMasterRPC: Connected to master at 
> localhost:35872
> 15/10/30 11:26:03 INFO agent.MultiMasterRPC: 
> 15/10/30 11:26:03 INFO agent.AvroMasterRPC: Connected to master at 
> localhost:35872
> please kindly suggest me.



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

[jira] [Commented] (FLUME-2831) Flume 0.9.4 : Windows client : Unable to start HTTP server

2015-10-30 Thread Gonzalo Herreros (JIRA) 

[ 
https://issues.apache.org/jira/browse/FLUME-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14982152#comment-14982152
 ] 

Gonzalo Herreros commented on FLUME-2831:
-

Flume is Java and doesn't have any native code AFAIK, so it should run on 
Windows the same.

If you download the tar.gz, on the bin folder there is run script for Windows: 
flume-ng.cmd
Note the configuration is very different from the version you have.

> Flume 0.9.4 : Windows client :  Unable to start HTTP server
> ---
>
> Key: FLUME-2831
> URL: https://issues.apache.org/jira/browse/FLUME-2831
> Project: Flume
>  Issue Type: IT Help
>  Components: Node
>Affects Versions: v0.9.4
> Environment: Node OS : Windows 8
> Master OS : CentOS 6.4
>Reporter: Pramod
>
> We are trying to collect log files collected on a Windows machine into CentOS 
> collector. Flume master is placed on the CentOS machine. 
> While starting the flume node on Windows node, we are getting the below 
> messages :
> 1. com.cloudera.util.InternalHttpServer$InternalHttpServerException: Unable 
> to start HTTP server
> 2. 15/10/29 11:46:13 INFO agent.MultiMasterRPC: No active master RPC 
> connection
> 15/10/29 11:46:14 WARN agent.MultiMasterRPC: Could not connect to any master 
> nodes (tried 1: [localhost:35872])
> Kindly assist



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

[jira] [Created] (FLUME-2834) TIBCO JMS with SSL enable

2015-10-30 Thread Sushma (JIRA) 
Sushma created FLUME-2834:
-

 Summary: TIBCO JMS with SSL enable
 Key: FLUME-2834
 URL: https://issues.apache.org/jira/browse/FLUME-2834
 Project: Flume
  Issue Type: Question
  Components: Sinks+Sources
Affects Versions: v1.4.0
 Environment: linux
Reporter: Sushma


I am trying to use JMS source with ssl enabled, but i am facing issues, below 
is my config for the jms source ...


agent.sources.mySrc.type = jms
agent.sources.mySrc.initialContextFactory = 
com.tibco.tibjms.naming.TibjmsInitialContextFactory
agent.sources.mySrc.providerURL = tibjmsnaming://:
agent.sources.mySrc.destinationName = MYQUEUE
agent.sources.mySrc.destinationType = queue
agent.sources.mySrc.batchSize=50
agent.sources.mySrc.connectionFactory = QueueConnectionFactory
agent.sources.mySrc.userName=user
agent.sources.mySrc.passwordFile=/opt/flume/conf/password.txt
agent.sources.mySrc.converter.type=org.apache.flume.source.jms.ELFJMSMessageEventUUIDConverter$Builder

agent.sources.mySrc.selector.type = multiplexing
agent.sources.mySrc.selector.header=zone
agent.sources.mySrc.selector.optional.TIBCO = myChannel1 myChannel2
agent.sources.mySrc.selector.optional.COMMON = myChannel1 

# SSL properties for JMS source mySrc 
agent.sources.mySrc.ssl=true
agent.sources.mySrc.keystore=/opt/flume/conf/jmsSslKey.store
agent.sources.mySrc.keystore-password=/opt/flume/conf/jmsPassword.txt
agent.sources.mySrc.keystore-type= store



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

[jira] [Commented] (FLUME-2712) Optional channel errors slows down the Source to Main channel event rate

2015-10-30 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/FLUME-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14983607#comment-14983607
 ] 

ASF subversion and git services commented on FLUME-2712:


Commit a7ffb27014f5808633f829b5f1e72a0290bd35a5 in flume's branch 
refs/heads/flume-1.7 from [~hshreedharan]
[ https://git-wip-us.apache.org/repos/asf?p=flume.git;h=a7ffb27 ]

FLUME-2712. Optional channel errors slows down the Source to Main channel event 
rate

(Johny Rufus via Hari)


> Optional channel errors slows down the Source to Main channel event rate
> 
>
> Key: FLUME-2712
> URL: https://issues.apache.org/jira/browse/FLUME-2712
> Project: Flume
>  Issue Type: Bug
>Reporter: Johny Rufus
>Assignee: Johny Rufus
> Attachments: FLUME-2712-1.patch, FLUME-2712-2.patch, 
> FLUME-2712.patch, FLUME-2712.patch
>
>
> When we have a source configured to deliver events to a main channel and an 
> optional channel, and if the delivery to optional channel fails, this 
> significantly slows down the rate at which events are delivered to the main 
> channel by the source.
> We need to evaluate async means of delivering events to the optional channel 
> and isolate the errors happening in optional channel from the delivery to the 
> main channel



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

[jira] [Updated] (FLUME-2835) Hive Sink tests need to create table with transactional property set

2015-10-30 Thread Sriharsha Chintalapani (JIRA) 

 [ 
https://issues.apache.org/jira/browse/FLUME-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sriharsha Chintalapani updated FLUME-2835:
--
Attachment: FLUME-hive-test.patch

>  Hive Sink tests need to create table with transactional property set
> -
>
> Key: FLUME-2835
> URL: https://issues.apache.org/jira/browse/FLUME-2835
> Project: Flume
>  Issue Type: Bug
>Reporter: Sriharsha Chintalapani
>Assignee: Sriharsha Chintalapani
> Attachments: FLUME-hive-test.patch
>
>
> As per Hive streaming wiki the  transactional=true property needs to be set 
> on the table for streaming. 
> https://cwiki.apache.org/confluence/display/Hive/Streaming+Data+Ingest



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

[jira] [Commented] (FLUME-2712) Optional channel errors slows down the Source to Main channel event rate

2015-10-30 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/FLUME-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14983597#comment-14983597
 ] 

ASF subversion and git services commented on FLUME-2712:


Commit 8bb556604047974775eb2da4c5c1686d89fe62d2 in flume's branch 
refs/heads/trunk from [~hshreedharan]
[ https://git-wip-us.apache.org/repos/asf?p=flume.git;h=8bb5566 ]

FLUME-2712. Optional channel errors slows down the Source to Main channel event 
rate

(Johny Rufus via Hari)


> Optional channel errors slows down the Source to Main channel event rate
> 
>
> Key: FLUME-2712
> URL: https://issues.apache.org/jira/browse/FLUME-2712
> Project: Flume
>  Issue Type: Bug
>Reporter: Johny Rufus
>Assignee: Johny Rufus
> Attachments: FLUME-2712-1.patch, FLUME-2712-2.patch, 
> FLUME-2712.patch, FLUME-2712.patch
>
>
> When we have a source configured to deliver events to a main channel and an 
> optional channel, and if the delivery to optional channel fails, this 
> significantly slows down the rate at which events are delivered to the main 
> channel by the source.
> We need to evaluate async means of delivering events to the optional channel 
> and isolate the errors happening in optional channel from the delivery to the 
> main channel



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

[jira] [Commented] (FLUME-2831) Flume 0.9.4 : Windows client : Unable to start HTTP server

2015-10-30 Thread Pramod (JIRA) 

[ 
https://issues.apache.org/jira/browse/FLUME-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14982223#comment-14982223
 ] 

Pramod commented on FLUME-2831:
---

Hello Gonzalo Herreros,

right we are using apache cloudera5.1 in centos. in that there is  no windows 
script for flume-ng.cmd.
so now we have to use apache-6.1 in both machine windows as well CentOs,  
version may not  issue.


Kindly assist

> Flume 0.9.4 : Windows client :  Unable to start HTTP server
> ---
>
> Key: FLUME-2831
> URL: https://issues.apache.org/jira/browse/FLUME-2831
> Project: Flume
>  Issue Type: IT Help
>  Components: Node
>Affects Versions: v0.9.4
> Environment: Node OS : Windows 8
> Master OS : CentOS 6.4
>Reporter: Pramod
>
> We are trying to collect log files collected on a Windows machine into CentOS 
> collector. Flume master is placed on the CentOS machine. 
> While starting the flume node on Windows node, we are getting the below 
> messages :
> 1. com.cloudera.util.InternalHttpServer$InternalHttpServerException: Unable 
> to start HTTP server
> 2. 15/10/29 11:46:13 INFO agent.MultiMasterRPC: No active master RPC 
> connection
> 15/10/29 11:46:14 WARN agent.MultiMasterRPC: Could not connect to any master 
> nodes (tried 1: [localhost:35872])
> Kindly assist



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

[jira] [Commented] (FLUME-2831) Flume 0.9.4 : Windows client : Unable to start HTTP server

2015-10-30 Thread Pramod (JIRA) 

[ 
https://issues.apache.org/jira/browse/FLUME-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14982269#comment-14982269
 ] 

Pramod commented on FLUME-2831:
---

can we install cygwin in windows to run flume please suggest me.

> Flume 0.9.4 : Windows client :  Unable to start HTTP server
> ---
>
> Key: FLUME-2831
> URL: https://issues.apache.org/jira/browse/FLUME-2831
> Project: Flume
>  Issue Type: IT Help
>  Components: Node
>Affects Versions: v0.9.4
> Environment: Node OS : Windows 8
> Master OS : CentOS 6.4
>Reporter: Pramod
>
> We are trying to collect log files collected on a Windows machine into CentOS 
> collector. Flume master is placed on the CentOS machine. 
> While starting the flume node on Windows node, we are getting the below 
> messages :
> 1. com.cloudera.util.InternalHttpServer$InternalHttpServerException: Unable 
> to start HTTP server
> 2. 15/10/29 11:46:13 INFO agent.MultiMasterRPC: No active master RPC 
> connection
> 15/10/29 11:46:14 WARN agent.MultiMasterRPC: Could not connect to any master 
> nodes (tried 1: [localhost:35872])
> Kindly assist



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

[jira] [Commented] (FLUME-2831) Flume 0.9.4 : Windows client : Unable to start HTTP server

2015-10-30 Thread Pramod (JIRA) 

[ 
https://issues.apache.org/jira/browse/FLUME-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14982345#comment-14982345
 ] 

Pramod commented on FLUME-2831:
---

Hello Gonzalo Herreros,

Please can u  send me any document on this.
to  krishnareddy.rev...@gmail.com very urgent.




> Flume 0.9.4 : Windows client :  Unable to start HTTP server
> ---
>
> Key: FLUME-2831
> URL: https://issues.apache.org/jira/browse/FLUME-2831
> Project: Flume
>  Issue Type: IT Help
>  Components: Node
>Affects Versions: v0.9.4
> Environment: Node OS : Windows 8
> Master OS : CentOS 6.4
>Reporter: Pramod
>
> We are trying to collect log files collected on a Windows machine into CentOS 
> collector. Flume master is placed on the CentOS machine. 
> While starting the flume node on Windows node, we are getting the below 
> messages :
> 1. com.cloudera.util.InternalHttpServer$InternalHttpServerException: Unable 
> to start HTTP server
> 2. 15/10/29 11:46:13 INFO agent.MultiMasterRPC: No active master RPC 
> connection
> 15/10/29 11:46:14 WARN agent.MultiMasterRPC: Could not connect to any master 
> nodes (tried 1: [localhost:35872])
> Kindly assist



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

[jira] [Commented] (FLUME-2832) Caught exception during HTTP server start

2015-10-30 Thread Pramod (JIRA) 

[ 
https://issues.apache.org/jira/browse/FLUME-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14982259#comment-14982259
 ] 

Pramod commented on FLUME-2832:
---

can we use apche 1.6 in both machines windows as well  CentOs

> Caught exception during HTTP server start
> -
>
> Key: FLUME-2832
> URL: https://issues.apache.org/jira/browse/FLUME-2832
> Project: Flume
>  Issue Type: Bug
>  Components: Node
>Affects Versions: v0.9.4
> Environment:  'flume-node-0.9.4' on Windows 8 (Node 1)
> and another in cent os 6.5 (node 2)
>Reporter: Harikrishna
>
> I have installed 'flume-node-0.9.4' on Windows 8 (Node 1)
> and another in cent os 6.5 (node 2)
> i have to pull the data from windows to linux using flume agent from windows
> my windows log files in E:/success/logs
> so i'm not enable to localhost on 35872 in windows agent.
> 15/10/30 11:25:58 WARN util.InternalHttpServer: Caught exception during HTTP 
> server start.
> java.net.BindException: Address already in use: bind
>   at sun.nio.ch.Net.bind0(Native Method)
>   at sun.nio.ch.Net.bind(Unknown Source)
>   at sun.nio.ch.Net.bind(Unknown Source)
>   at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
>   at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
>   at 
> org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:216)
>   at 
> org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:315)
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>   at org.mortbay.jetty.Server.doStart(Server.java:235)
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>   at 
> com.cloudera.util.InternalHttpServer.start(InternalHttpServer.java:188)
>   at com.cloudera.flume.agent.FlumeNode.start(FlumeNode.java:275)
>   at 
> com.cloudera.flume.agent.FlumeNodeDaemon.start(FlumeNodeDaemon.java:86)
>   at 
> com.cloudera.flume.agent.FlumeNodeDaemon.windowsService(FlumeNodeDaemon.java:54)
> 15/10/30 11:25:58 ERROR agent.FlumeNode: Unexpected exception/error thrown! 
> Unable to start HTTP server
> com.cloudera.util.InternalHttpServer$InternalHttpServerException: Unable to 
> start HTTP server
>   at 
> com.cloudera.util.InternalHttpServer.start(InternalHttpServer.java:194)
>   at com.cloudera.flume.agent.FlumeNode.start(FlumeNode.java:275)
>   at 
> com.cloudera.flume.agent.FlumeNodeDaemon.start(FlumeNodeDaemon.java:86)
>   at 
> com.cloudera.flume.agent.FlumeNodeDaemon.windowsService(FlumeNodeDaemon.java:54)
> Caused by: java.net.BindException: Address already in use: bind
>   at sun.nio.ch.Net.bind0(Native Method)
>   at sun.nio.ch.Net.bind(Unknown Source)
>   at sun.nio.ch.Net.bind(Unknown Source)
>   at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
>   at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
>   at 
> org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:216)
>   at 
> org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:315)
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>   at org.mortbay.jetty.Server.doStart(Server.java:235)
>   at 
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>   at 
> com.cloudera.util.InternalHttpServer.start(InternalHttpServer.java:188)
>   ... 3 more
> 15/10/30 11:25:58 INFO agent.MultiMasterRPC: 
> 15/10/30 11:25:58 INFO agent.AvroMasterRPC: Connected to master at 
> localhost:35872
> 15/10/30 11:26:02 INFO agent.MultiMasterRPC: 
> 15/10/30 11:26:02 INFO agent.AvroMasterRPC: Connected to master at 
> localhost:35872
> 15/10/30 11:26:03 INFO agent.MultiMasterRPC: 
> 15/10/30 11:26:03 INFO agent.AvroMasterRPC: Connected to master at 
> localhost:35872
> please kindly suggest me.



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

[jira] [Commented] (FLUME-2712) Optional channel errors slows down the Source to Main channel event rate

2015-10-30 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/FLUME-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14983712#comment-14983712
 ] 

Hudson commented on FLUME-2712:
---

UNSTABLE: Integrated in Flume-trunk-hbase-1 #132 (See 
[https://builds.apache.org/job/Flume-trunk-hbase-1/132/])
FLUME-2712. Optional channel errors slows down the Source to Main 
(hshreedharan: 
[http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git=commit=8bb556604047974775eb2da4c5c1686d89fe62d2])
* flume-ng-core/src/test/java/org/apache/flume/channel/TestChannelProcessor.java
* flume-ng-core/src/main/java/org/apache/flume/channel/ChannelProcessor.java


> Optional channel errors slows down the Source to Main channel event rate
> 
>
> Key: FLUME-2712
> URL: https://issues.apache.org/jira/browse/FLUME-2712
> Project: Flume
>  Issue Type: Bug
>Reporter: Johny Rufus
>Assignee: Johny Rufus
> Attachments: FLUME-2712-1.patch, FLUME-2712-2.patch, 
> FLUME-2712.patch, FLUME-2712.patch
>
>
> When we have a source configured to deliver events to a main channel and an 
> optional channel, and if the delivery to optional channel fails, this 
> significantly slows down the rate at which events are delivered to the main 
> channel by the source.
> We need to evaluate async means of delivering events to the optional channel 
> and isolate the errors happening in optional channel from the delivery to the 
> main channel



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

Jenkins build is still unstable: Flume-trunk-hbase-1 #132

2015-10-30 Thread Apache Jenkins Server 
See

[jira] [Created] (FLUME-2835) Hive Sink tests need to create table with transactional property set

2015-10-30 Thread Sriharsha Chintalapani (JIRA) 
Sriharsha Chintalapani created FLUME-2835:
-

 Summary:  Hive Sink tests need to create table with transactional 
property set
 Key: FLUME-2835
 URL: https://issues.apache.org/jira/browse/FLUME-2835
 Project: Flume
  Issue Type: Bug
Reporter: Sriharsha Chintalapani
Assignee: Sriharsha Chintalapani


As per Hive streaming wiki the  transactional=true property needs to be set on 
the table for streaming. 
https://cwiki.apache.org/confluence/display/Hive/Streaming+Data+Ingest



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

[jira] [Commented] (FLUME-2712) Optional channel errors slows down the Source to Main channel event rate

2015-10-30 Thread Hari Shreedharan (JIRA) 

[ 
https://issues.apache.org/jira/browse/FLUME-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14983371#comment-14983371
 ] 

Hari Shreedharan commented on FLUME-2712:
-

+1. LGTM. Running tests and committing

> Optional channel errors slows down the Source to Main channel event rate
> 
>
> Key: FLUME-2712
> URL: https://issues.apache.org/jira/browse/FLUME-2712
> Project: Flume
>  Issue Type: Bug
>Reporter: Johny Rufus
>Assignee: Johny Rufus
> Attachments: FLUME-2712-1.patch, FLUME-2712-2.patch, 
> FLUME-2712.patch, FLUME-2712.patch
>
>
> When we have a source configured to deliver events to a main channel and an 
> optional channel, and if the delivery to optional channel fails, this 
> significantly slows down the rate at which events are delivered to the main 
> channel by the source.
> We need to evaluate async means of delivering events to the optional channel 
> and isolate the errors happening in optional channel from the delivery to the 
> main channel



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

[jira] [Created] (FLUME-2833) Implement a "replicating" sink processor

2015-10-30 Thread li xiang (JIRA) 
li xiang created FLUME-2833:
---

 Summary: Implement a "replicating" sink processor
 Key: FLUME-2833
 URL: https://issues.apache.org/jira/browse/FLUME-2833
 Project: Flume
  Issue Type: Improvement
  Components: Sinks+Sources
Reporter: li xiang






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

[jira] [Updated] (FLUME-2833) Implement a "replicating" sink processor

2015-10-30 Thread li xiang (JIRA) 

 [ 
https://issues.apache.org/jira/browse/FLUME-2833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

li xiang updated FLUME-2833:

Description: 
As proposed by Yongkun in FLUME-1435, it is a common scenario where
1. More than one sink is connected a single channel
2. Each event in the channel is replicated and pushed into all sinks

But the current sink processors(default, failover, load_balance) can not 
implement that request. 
Yongkun‘s proposal in FLME-1435 is complicated. As the first step, a 
"replicating" sink process can be implemented.  

> Implement a "replicating" sink processor
> 
>
> Key: FLUME-2833
> URL: https://issues.apache.org/jira/browse/FLUME-2833
> Project: Flume
>  Issue Type: Improvement
>  Components: Sinks+Sources
>Reporter: li xiang
>
> As proposed by Yongkun in FLUME-1435, it is a common scenario where
> 1. More than one sink is connected a single channel
> 2. Each event in the channel is replicated and pushed into all sinks
> But the current sink processors(default, failover, load_balance) can not 
> implement that request. 
> Yongkun‘s proposal in FLME-1435 is complicated. As the first step, a 
> "replicating" sink process can be implemented.  



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

[jira] [Commented] (FLUME-2831) Flume 0.9.4 : Windows client : Unable to start HTTP server

2015-10-30 Thread Gonzalo Herreros (JIRA) 

[ 
https://issues.apache.org/jira/browse/FLUME-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14982314#comment-14982314
 ] 

Gonzalo Herreros commented on FLUME-2831:
-

cygwin won't help.
I would just download Flume from Apache to run on Windows and use a sink that 
submits to the Cloudera Flume version on CentOs.

> Flume 0.9.4 : Windows client :  Unable to start HTTP server
> ---
>
> Key: FLUME-2831
> URL: https://issues.apache.org/jira/browse/FLUME-2831
> Project: Flume
>  Issue Type: IT Help
>  Components: Node
>Affects Versions: v0.9.4
> Environment: Node OS : Windows 8
> Master OS : CentOS 6.4
>Reporter: Pramod
>
> We are trying to collect log files collected on a Windows machine into CentOS 
> collector. Flume master is placed on the CentOS machine. 
> While starting the flume node on Windows node, we are getting the below 
> messages :
> 1. com.cloudera.util.InternalHttpServer$InternalHttpServerException: Unable 
> to start HTTP server
> 2. 15/10/29 11:46:13 INFO agent.MultiMasterRPC: No active master RPC 
> connection
> 15/10/29 11:46:14 WARN agent.MultiMasterRPC: Could not connect to any master 
> nodes (tried 1: [localhost:35872])
> Kindly assist



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

[jira] [Updated] (FLUME-2712) Optional channel errors slows down the Source to Main channel event rate

2015-10-30 Thread Johny Rufus (JIRA) 

 [ 
https://issues.apache.org/jira/browse/FLUME-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Johny Rufus updated FLUME-2712:
---
Attachment: FLUME-2712-2.patch

[~hshreedharan], Attaching patch with review comments incorporated

> Optional channel errors slows down the Source to Main channel event rate
> 
>
> Key: FLUME-2712
> URL: https://issues.apache.org/jira/browse/FLUME-2712
> Project: Flume
>  Issue Type: Bug
>Reporter: Johny Rufus
>Assignee: Johny Rufus
> Attachments: FLUME-2712-1.patch, FLUME-2712-2.patch, 
> FLUME-2712.patch, FLUME-2712.patch
>
>
> When we have a source configured to deliver events to a main channel and an 
> optional channel, and if the delivery to optional channel fails, this 
> significantly slows down the rate at which events are delivered to the main 
> channel by the source.
> We need to evaluate async means of delivering events to the optional channel 
> and isolate the errors happening in optional channel from the delivery to the 
> main channel



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

Re: Review Request 39035: FLUME-2712: Optional channel errors slows down the Source to Main channel event rate

2015-10-30 Thread Johny Rufus John 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39035/
---

(Updated Oct. 30, 2015, 8:13 p.m.)


Review request for Flume.


Bugs: FLUME-2712
https://issues.apache.org/jira/browse/FLUME-2712


Repository: flume-git


Description
---

Optional channel errors slows down the Source to Main channel event rate. This 
change makes delivery to optional channel asynchronously.


Diffs (updated)
-

  flume-ng-core/src/main/java/org/apache/flume/channel/ChannelProcessor.java 
1cce137 
  
flume-ng-core/src/test/java/org/apache/flume/channel/TestChannelProcessor.java 
0656596 

Diff: https://reviews.apache.org/r/39035/diff/


Testing
---

Tested with optional channel setup to observe the performance improvement


Thanks,

Johny Rufus John