[jira] [Commented] (FLUME-2831) Flume 0.9.4 : Windows client : Unable to start HTTP server
[ https://issues.apache.org/jira/browse/FLUME-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981976#comment-14981976 ] Pramod commented on FLUME-2831: --- Hello Gonzalo Herreos, we are right now working through root privileges only. and also we changed different port numbers it's showing same issue, if we want to change flume version to 1.6 we are not finding any windows version on this, can u please kindly suggest me on it. > 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-2832) Caught exception during HTTP server start
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-2712) Optional channel errors slows down the Source to Main channel event rate
[
https://issues.apache.org/jira/browse/FLUME-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981879#comment-14981879
]
Hari Shreedharan commented on FLUME-2712:
-
Johny,
This looks good in general. Some minor comments:
* I think the {{executeRequiredChannelTransaction}} can be
{{executeChannelTransaction}} and can be used for both. Just take an additional
flag as an argument and throw the {{ChannelException}} based on that. Otherwise
the run method in {{OptionalChannelTransactionExecutor}} are exactly the same
* {{OptionalChannelTransactionExecutor}} should be named
{{OptionalChannelTransactionThread}} or something like that - it really is not
an executor.
* {{List events = new ArrayList()}} -> {{List events = new
ArrayList(1)}} in {{processEvent}} method.
> 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.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-2781) A Kafka Channel defined as parseAsFlumeEvent=false cannot be correctly used by a Flume source
[ https://issues.apache.org/jira/browse/FLUME-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Jarcec Cecho updated FLUME-2781: -- Fix Version/s: v1.7.0 > A Kafka Channel defined as parseAsFlumeEvent=false cannot be correctly used > by a Flume source > - > > Key: FLUME-2781 > URL: https://issues.apache.org/jira/browse/FLUME-2781 > Project: Flume > Issue Type: Improvement >Affects Versions: v1.6.0 >Reporter: Gonzalo Herreros >Assignee: Gonzalo Herreros > Labels: easyfix, patch > Fix For: v1.7.0 > > Attachments: FLUME-2781.patch > > > When a Kafka channel is configured as parseAsFlumeEvent=false, the channel > will read events from the topic as text instead of serialized Avro Flume > events. > This is useful so Flume can read from an existing Kafka topic, where other > Kafka clients publish as text. > However, if you use a Flume source on that channel, it will still write the > events as Avro so it will create an inconsistency and those events will fail > to be read correctly. > Also, this would allow a Flume source to write to a Kafka channel and any > Kafka subscriber to listen to Flume events passing through without binary > dependencies. -- 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
[ https://issues.apache.org/jira/browse/FLUME-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980041#comment-14980041 ] Gonzalo Herreros commented on FLUME-2831: - There has to be additional information about why the HTTP server failed to start. My guess is that you are trying to open a privileged port without having root user or maybe the port is taken already. Anyway, the version you are using is obsolete and very different from the current one (1.6.0). I suggest you upgrade because you won't get fixes in yours. > 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-2831) Flume 0.9.4 : Windows client : Unable to start HTTP server
Pramod created FLUME-2831: - Summary: 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)
