[jira] [Commented] (FLUME-2752) Flume AvroSoucr will leak the memory and the OOM will be happened.

2015-07-29 Thread yinghua_zh (JIRA) 

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

yinghua_zh commented on FLUME-2752:
---

if the nettyserver start failed,we should invoke the close methed,the close 
method will release the resource:

try {
server.start();
} catch (Exception e1) {
logger.error("start sever failed:", e1);
server.close();
throw new RuntimeException(e1);
}

> Flume AvroSoucr will leak the memory and the OOM will be happened.
> --
>
> Key: FLUME-2752
> URL: https://issues.apache.org/jira/browse/FLUME-2752
> Project: Flume
>  Issue Type: Bug
>  Components: Sinks+Sources
>Affects Versions: v1.6.0
>Reporter: yinghua_zh
>
> If the flume agent config the nonexist IP for the avro source,the exception 
> will be happened as follow:
> 2015-07-21 19:57:47,054 | ERROR | [lifecycleSupervisor-1-2] |  Unable to 
> start EventDrivenSourceRunner: { source:Avro source avro_source_21155: { 
> bindAddress: 51.196.27.32, port: 21155 } } - Exception follows.  | 
> org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:253)
> org.jboss.netty.channel.ChannelException: Failed to bind to: 
> /51.196.27.32:21155
>   at 
> org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:297)
>   at org.apache.avro.ipc.NettyServer.(NettyServer.java:106)
>   at org.apache.flume.source.AvroSource.start(AvroSource.java:294)
>   at 
> org.apache.flume.source.EventDrivenSourceRunner.start(EventDrivenSourceRunner.java:44)
>   at 
> org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:251)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.BindException: Cannot assign requested address
>   at sun.nio.ch.Net.bind0(Native Method)
>   at sun.nio.ch.Net.bind(Net.java:437)
>   at sun.nio.ch.Net.bind(Net.java:429)
>   at 
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
>   at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.bind(NioServerSocketPipelineSink.java:140)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleServerSocket(NioServerSocketPipelineSink.java:90)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:64)
>   at org.jboss.netty.channel.Channels.bind(Channels.java:569)
>   at 
> org.jboss.netty.channel.AbstractChannel.bind(AbstractChannel.java:189)
>   at 
> org.jboss.netty.bootstrap.ServerBootstrap$Binder.channelOpen(ServerBootstrap.java:342)
>   at org.jboss.netty.channel.Channels.fireChannelOpen(Channels.java:170)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketChannel.(NioServerSocketChannel.java:80)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:158)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:86)
>   at 
> org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:276)
> if the above exception happened for 2 hours,and the agent JVM -Xxx is 4G,the 
> OutOfMemory will be happened.



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

Hive test failures

2015-07-29 Thread Hari Shreedharan 
Hi,

It looks like Hive tests have been failing for a while now:
https://builds.apache.org/job/Flume-trunk-hbase-1/116/#showFailuresLink

Any idea what is happening here - it seems like it is something related to
the scratch directory not being writable.

Thanks,
Hari

[jira] [Commented] (FLUME-2752) Flume AvroSoucr will leak the memory and the OOM will be happened.

2015-07-29 Thread Hari Shreedharan (JIRA) 

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

Hari Shreedharan commented on FLUME-2752:
-

Good catch! We should make sure we do shutdown the thread pool if the start 
fails.

> Flume AvroSoucr will leak the memory and the OOM will be happened.
> --
>
> Key: FLUME-2752
> URL: https://issues.apache.org/jira/browse/FLUME-2752
> Project: Flume
>  Issue Type: Bug
>  Components: Sinks+Sources
>Affects Versions: v1.6.0
>Reporter: yinghua_zh
>
> If the flume agent config the nonexist IP for the avro source,the exception 
> will be happened as follow:
> 2015-07-21 19:57:47,054 | ERROR | [lifecycleSupervisor-1-2] |  Unable to 
> start EventDrivenSourceRunner: { source:Avro source avro_source_21155: { 
> bindAddress: 51.196.27.32, port: 21155 } } - Exception follows.  | 
> org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:253)
> org.jboss.netty.channel.ChannelException: Failed to bind to: 
> /51.196.27.32:21155
>   at 
> org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:297)
>   at org.apache.avro.ipc.NettyServer.(NettyServer.java:106)
>   at org.apache.flume.source.AvroSource.start(AvroSource.java:294)
>   at 
> org.apache.flume.source.EventDrivenSourceRunner.start(EventDrivenSourceRunner.java:44)
>   at 
> org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:251)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.BindException: Cannot assign requested address
>   at sun.nio.ch.Net.bind0(Native Method)
>   at sun.nio.ch.Net.bind(Net.java:437)
>   at sun.nio.ch.Net.bind(Net.java:429)
>   at 
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
>   at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.bind(NioServerSocketPipelineSink.java:140)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleServerSocket(NioServerSocketPipelineSink.java:90)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:64)
>   at org.jboss.netty.channel.Channels.bind(Channels.java:569)
>   at 
> org.jboss.netty.channel.AbstractChannel.bind(AbstractChannel.java:189)
>   at 
> org.jboss.netty.bootstrap.ServerBootstrap$Binder.channelOpen(ServerBootstrap.java:342)
>   at org.jboss.netty.channel.Channels.fireChannelOpen(Channels.java:170)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketChannel.(NioServerSocketChannel.java:80)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:158)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:86)
>   at 
> org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:276)
> if the above exception happened for 2 hours,and the agent JVM -Xxx is 4G,the 
> OutOfMemory will be happened.



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

[jira] [Comment Edited] (FLUME-2752) Flume AvroSoucr will leak the memory and the OOM will be happened.

2015-07-29 Thread yinghua_zh (JIRA) 

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

yinghua_zh edited comment on FLUME-2752 at 7/30/15 2:33 AM:


The avro soucr start method will start thread pool,but the NettyServer init 
failed,and the thread pool does not shutdown,Then the memory will be leaked,and 
the next 3 seconds will start avso source and it will start thread pool,and the 
NettyServer init failed,and the thread pool does not shutdown,So the 
OutOfMemory will be happened finally.


was (Author: yinghua_zh):
The avro soucr start method will start thread pool,but the NettyServer init 
failed,and the thread pool does not shutdown,Then the memory will be leaked,and 
the next 3 seconds will start avso source and it will start thread pool,and the 
NettyServer initfailed,and the thread pool does not shutdown,So the OutOfMemory 
will be happened finally.

> Flume AvroSoucr will leak the memory and the OOM will be happened.
> --
>
> Key: FLUME-2752
> URL: https://issues.apache.org/jira/browse/FLUME-2752
> Project: Flume
>  Issue Type: Bug
>  Components: Sinks+Sources
>Affects Versions: v1.6.0
>Reporter: yinghua_zh
>
> If the flume agent config the nonexist IP for the avro source,the exception 
> will be happened as follow:
> 2015-07-21 19:57:47,054 | ERROR | [lifecycleSupervisor-1-2] |  Unable to 
> start EventDrivenSourceRunner: { source:Avro source avro_source_21155: { 
> bindAddress: 51.196.27.32, port: 21155 } } - Exception follows.  | 
> org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:253)
> org.jboss.netty.channel.ChannelException: Failed to bind to: 
> /51.196.27.32:21155
>   at 
> org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:297)
>   at org.apache.avro.ipc.NettyServer.(NettyServer.java:106)
>   at org.apache.flume.source.AvroSource.start(AvroSource.java:294)
>   at 
> org.apache.flume.source.EventDrivenSourceRunner.start(EventDrivenSourceRunner.java:44)
>   at 
> org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:251)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.BindException: Cannot assign requested address
>   at sun.nio.ch.Net.bind0(Native Method)
>   at sun.nio.ch.Net.bind(Net.java:437)
>   at sun.nio.ch.Net.bind(Net.java:429)
>   at 
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
>   at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.bind(NioServerSocketPipelineSink.java:140)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleServerSocket(NioServerSocketPipelineSink.java:90)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:64)
>   at org.jboss.netty.channel.Channels.bind(Channels.java:569)
>   at 
> org.jboss.netty.channel.AbstractChannel.bind(AbstractChannel.java:189)
>   at 
> org.jboss.netty.bootstrap.ServerBootstrap$Binder.channelOpen(ServerBootstrap.java:342)
>   at org.jboss.netty.channel.Channels.fireChannelOpen(Channels.java:170)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketChannel.(NioServerSocketChannel.java:80)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:158)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:86)
>   at 
> org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:276)
> if the above exception happened for 2 hours,and the agent JVM -Xxx is 4G,the 
> OutOfMemory will be happened.



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

[jira] [Comment Edited] (FLUME-2752) Flume AvroSoucr will leak the memory and the OOM will be happened.

2015-07-29 Thread yinghua_zh (JIRA) 

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

yinghua_zh edited comment on FLUME-2752 at 7/30/15 2:32 AM:


The avro soucr start method will start thread pool,but the NettyServer init 
failed,and the thread pool does not shutdown,Then the memory will be leaked,and 
the next 3 seconds will start avso source and it will start thread pool,and the 
NettyServer initfailed,and the thread pool does not shutdown,So the OutOfMemory 
will be happened finally.


was (Author: yinghua_zh):
The avro soucr start method will start thread pool,but the NettyServer start 
failed,and the thread pool does not shutdown,Then the memory will be leaked,and 
the next 3 seconds will start avso source and it will start thread pool,and the 
NettyServer start failed,and the thread pool does not shutdown,So the 
OutOfMemory will be happened finally.

> Flume AvroSoucr will leak the memory and the OOM will be happened.
> --
>
> Key: FLUME-2752
> URL: https://issues.apache.org/jira/browse/FLUME-2752
> Project: Flume
>  Issue Type: Bug
>  Components: Sinks+Sources
>Affects Versions: v1.6.0
>Reporter: yinghua_zh
>
> If the flume agent config the nonexist IP for the avro source,the exception 
> will be happened as follow:
> 2015-07-21 19:57:47,054 | ERROR | [lifecycleSupervisor-1-2] |  Unable to 
> start EventDrivenSourceRunner: { source:Avro source avro_source_21155: { 
> bindAddress: 51.196.27.32, port: 21155 } } - Exception follows.  | 
> org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:253)
> org.jboss.netty.channel.ChannelException: Failed to bind to: 
> /51.196.27.32:21155
>   at 
> org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:297)
>   at org.apache.avro.ipc.NettyServer.(NettyServer.java:106)
>   at org.apache.flume.source.AvroSource.start(AvroSource.java:294)
>   at 
> org.apache.flume.source.EventDrivenSourceRunner.start(EventDrivenSourceRunner.java:44)
>   at 
> org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:251)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.BindException: Cannot assign requested address
>   at sun.nio.ch.Net.bind0(Native Method)
>   at sun.nio.ch.Net.bind(Net.java:437)
>   at sun.nio.ch.Net.bind(Net.java:429)
>   at 
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
>   at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.bind(NioServerSocketPipelineSink.java:140)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleServerSocket(NioServerSocketPipelineSink.java:90)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:64)
>   at org.jboss.netty.channel.Channels.bind(Channels.java:569)
>   at 
> org.jboss.netty.channel.AbstractChannel.bind(AbstractChannel.java:189)
>   at 
> org.jboss.netty.bootstrap.ServerBootstrap$Binder.channelOpen(ServerBootstrap.java:342)
>   at org.jboss.netty.channel.Channels.fireChannelOpen(Channels.java:170)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketChannel.(NioServerSocketChannel.java:80)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:158)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:86)
>   at 
> org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:276)
> if the above exception happened for 2 hours,and the agent JVM -Xxx is 4G,the 
> OutOfMemory will be happened.



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

[jira] [Comment Edited] (FLUME-2752) Flume AvroSoucr will leak the memory and the OOM will be happened.

2015-07-29 Thread yinghua_zh (JIRA) 

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

yinghua_zh edited comment on FLUME-2752 at 7/30/15 2:28 AM:


  @Override
  public void start() {
logger.info("Starting {}...", this);

Responder responder = new SpecificResponder(AvroSourceProtocol.class, this);
NioServerSocketChannelFactory socketChannelFactory = 
initSocketChannelFactory();
ChannelPipelineFactory pipelineFactory = initChannelPipelineFactory();


connectionCountUpdater = Executors.newSingleThreadScheduledExecutor();
server.start();
sourceCounter.start();
super.start();
final NettyServer srv = (NettyServer)server;
connectionCountUpdater.scheduleWithFixedDelay(new Runnable(){

  @Override
  public void run() {
sourceCounter.setOpenConnectionCount(
Long.valueOf(srv.getNumActiveConnections()));
  }
}, 0, 60, TimeUnit.SECONDS);

logger.info("Avro source {} started.", getName());
  }
I have modfye the code ,can you agree?

  @Override
  public void start() {
logger.info("Starting {}...", this);


Responder responder = new SpecificResponder(AvroSourceProtocol.class, this);
NioServerSocketChannelFactory socketChannelFactory = 
initSocketChannelFactory();
ChannelPipelineFactory pipelineFactory = initChannelPipelineFactory();
try
{
server = new NettyServer(responder, new InetSocketAddress(bindAddress, 
port),
   socketChannelFactory, pipelineFactory, null);
}catch (Exception ex){
try{
   socketChannelFactory.releaseExternalResources();
}
catch (Exception e1){
logger.error("realese ectrrnla resource occur exception:", e1);
}

try{
socketChannelFactory.releaseExternalResources();
} catch (Exception e2){
logger.error("realese ectrrnla resource occur exception:", e2);
}
throw new RuntimeException(ex);
}



connectionCountUpdater = Executors.newSingleThreadScheduledExecutor();
server.start();
sourceCounter.start();
super.start();
final NettyServer srv = (NettyServer)server;
connectionCountUpdater.scheduleWithFixedDelay(new Runnable(){

  @Override
  public void run() {
sourceCounter.setOpenConnectionCount(
Long.valueOf(srv.getNumActiveConnections()));
  }
}, 0, 60, TimeUnit.SECONDS);

logger.info("Avro source {} started.", getName());
  }






was (Author: yinghua_zh):
  @Override
  public void start() {
logger.info("Starting {}...", this);

Responder responder = new SpecificResponder(AvroSourceProtocol.class, this);
NioServerSocketChannelFactory socketChannelFactory = 
initSocketChannelFactory();
ChannelPipelineFactory pipelineFactory = initChannelPipelineFactory();


connectionCountUpdater = Executors.newSingleThreadScheduledExecutor();
server.start();
sourceCounter.start();
super.start();
final NettyServer srv = (NettyServer)server;
connectionCountUpdater.scheduleWithFixedDelay(new Runnable(){

  @Override
  public void run() {
sourceCounter.setOpenConnectionCount(
Long.valueOf(srv.getNumActiveConnections()));
  }
}, 0, 60, TimeUnit.SECONDS);

logger.info("Avro source {} started.", getName());
  }
I have modfye the code ,can you accept it?

  @Override
  public void start() {
logger.info("Starting {}...", this);


Responder responder = new SpecificResponder(AvroSourceProtocol.class, this);
NioServerSocketChannelFactory socketChannelFactory = 
initSocketChannelFactory();
ChannelPipelineFactory pipelineFactory = initChannelPipelineFactory();
try
{
server = new NettyServer(responder, new InetSocketAddress(bindAddress, 
port),
   socketChannelFactory, pipelineFactory, null);
}catch (Exception ex){
try{
   socketChannelFactory.releaseExternalResources();
}
catch (Exception e1){
logger.error("realese ectrrnla resource occur exception:", e1);
}

try{
socketChannelFactory.releaseExternalResources();
} catch (Exception e2){
logger.error("realese ectrrnla resource occur exception:", e2);
}
throw new RuntimeException(ex);
}



connectionCountUpdater = Executors.newSingleThreadScheduledExecutor();
server.start();
sourceCounter.start();
super.start();
final NettyServer srv = (NettyServer)server;
connectionCountUpdater.scheduleWithFixedDelay(new Runnable(){

  @Override
  public void run() {
sourceCounter.setOpenConnectionCount(
Long.valueOf(srv.getNumActiveConnections()));
  }
}, 0, 60, TimeUnit.SECOND

[jira] [Commented] (FLUME-2752) Flume AvroSoucr will leak the memory and the OOM will be happened.

2015-07-29 Thread yinghua_zh (JIRA) 

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

yinghua_zh commented on FLUME-2752:
---

  @Override
  public void start() {
logger.info("Starting {}...", this);

Responder responder = new SpecificResponder(AvroSourceProtocol.class, this);
NioServerSocketChannelFactory socketChannelFactory = 
initSocketChannelFactory();
ChannelPipelineFactory pipelineFactory = initChannelPipelineFactory();


connectionCountUpdater = Executors.newSingleThreadScheduledExecutor();
server.start();
sourceCounter.start();
super.start();
final NettyServer srv = (NettyServer)server;
connectionCountUpdater.scheduleWithFixedDelay(new Runnable(){

  @Override
  public void run() {
sourceCounter.setOpenConnectionCount(
Long.valueOf(srv.getNumActiveConnections()));
  }
}, 0, 60, TimeUnit.SECONDS);

logger.info("Avro source {} started.", getName());
  }
I have modfye the code ,can you accept it?

  @Override
  public void start() {
logger.info("Starting {}...", this);


Responder responder = new SpecificResponder(AvroSourceProtocol.class, this);
NioServerSocketChannelFactory socketChannelFactory = 
initSocketChannelFactory();
ChannelPipelineFactory pipelineFactory = initChannelPipelineFactory();
try
{
server = new NettyServer(responder, new InetSocketAddress(bindAddress, 
port),
   socketChannelFactory, pipelineFactory, null);
}catch (Exception ex){
try{
   socketChannelFactory.releaseExternalResources();
}
catch (Exception e1){
logger.error("realese ectrrnla resource occur exception:", e1);
}

try{
socketChannelFactory.releaseExternalResources();
} catch (Exception e2){
logger.error("realese ectrrnla resource occur exception:", e2);
}
throw new RuntimeException(ex);
}



connectionCountUpdater = Executors.newSingleThreadScheduledExecutor();
server.start();
sourceCounter.start();
super.start();
final NettyServer srv = (NettyServer)server;
connectionCountUpdater.scheduleWithFixedDelay(new Runnable(){

  @Override
  public void run() {
sourceCounter.setOpenConnectionCount(
Long.valueOf(srv.getNumActiveConnections()));
  }
}, 0, 60, TimeUnit.SECONDS);

logger.info("Avro source {} started.", getName());
  }





> Flume AvroSoucr will leak the memory and the OOM will be happened.
> --
>
> Key: FLUME-2752
> URL: https://issues.apache.org/jira/browse/FLUME-2752
> Project: Flume
>  Issue Type: Bug
>  Components: Sinks+Sources
>Affects Versions: v1.6.0
>Reporter: yinghua_zh
>
> If the flume agent config the nonexist IP for the avro source,the exception 
> will be happened as follow:
> 2015-07-21 19:57:47,054 | ERROR | [lifecycleSupervisor-1-2] |  Unable to 
> start EventDrivenSourceRunner: { source:Avro source avro_source_21155: { 
> bindAddress: 51.196.27.32, port: 21155 } } - Exception follows.  | 
> org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:253)
> org.jboss.netty.channel.ChannelException: Failed to bind to: 
> /51.196.27.32:21155
>   at 
> org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:297)
>   at org.apache.avro.ipc.NettyServer.(NettyServer.java:106)
>   at org.apache.flume.source.AvroSource.start(AvroSource.java:294)
>   at 
> org.apache.flume.source.EventDrivenSourceRunner.start(EventDrivenSourceRunner.java:44)
>   at 
> org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:251)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.BindException: Cannot assign requested address
>   at sun.nio.ch.Net.bind0(Native Method)
>   at sun.nio.ch.Net.bind(Net.java:437)
>   at sun.nio.ch.Net.bind(Net.java:429)
>   at 
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
>   at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.j

[jira] [Comment Edited] (FLUME-2752) Flume AvroSoucr will leak the memory and the OOM will be happened.

2015-07-29 Thread yinghua_zh (JIRA) 

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

yinghua_zh edited comment on FLUME-2752 at 7/30/15 2:25 AM:


The avro soucr start method will start thread pool,but the NettyServer start 
failed,and the thread pool does not shutdown,Then the memory will be leaked,and 
the next 3 seconds will start avso source and it will start thread pool,and the 
NettyServer start failed,and the thread pool does not shutdown,So the 
OutOfMemory will be happened finally.


was (Author: yinghua_zh):
The avro soucr start method will start thread pool,but the NettyServer start 
failed,and the thread pool does not shutdown,Then the memory will be leaked,and 
the next 3 seconds will start thread pool,and the NettyServer start failed,and 
the thread pool does not shutdown,So the OutOfMemory will be happened.

> Flume AvroSoucr will leak the memory and the OOM will be happened.
> --
>
> Key: FLUME-2752
> URL: https://issues.apache.org/jira/browse/FLUME-2752
> Project: Flume
>  Issue Type: Bug
>  Components: Sinks+Sources
>Affects Versions: v1.6.0
>Reporter: yinghua_zh
>
> If the flume agent config the nonexist IP for the avro source,the exception 
> will be happened as follow:
> 2015-07-21 19:57:47,054 | ERROR | [lifecycleSupervisor-1-2] |  Unable to 
> start EventDrivenSourceRunner: { source:Avro source avro_source_21155: { 
> bindAddress: 51.196.27.32, port: 21155 } } - Exception follows.  | 
> org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:253)
> org.jboss.netty.channel.ChannelException: Failed to bind to: 
> /51.196.27.32:21155
>   at 
> org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:297)
>   at org.apache.avro.ipc.NettyServer.(NettyServer.java:106)
>   at org.apache.flume.source.AvroSource.start(AvroSource.java:294)
>   at 
> org.apache.flume.source.EventDrivenSourceRunner.start(EventDrivenSourceRunner.java:44)
>   at 
> org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:251)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.BindException: Cannot assign requested address
>   at sun.nio.ch.Net.bind0(Native Method)
>   at sun.nio.ch.Net.bind(Net.java:437)
>   at sun.nio.ch.Net.bind(Net.java:429)
>   at 
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
>   at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.bind(NioServerSocketPipelineSink.java:140)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleServerSocket(NioServerSocketPipelineSink.java:90)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:64)
>   at org.jboss.netty.channel.Channels.bind(Channels.java:569)
>   at 
> org.jboss.netty.channel.AbstractChannel.bind(AbstractChannel.java:189)
>   at 
> org.jboss.netty.bootstrap.ServerBootstrap$Binder.channelOpen(ServerBootstrap.java:342)
>   at org.jboss.netty.channel.Channels.fireChannelOpen(Channels.java:170)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketChannel.(NioServerSocketChannel.java:80)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:158)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:86)
>   at 
> org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:276)
> if the above exception happened for 2 hours,and the agent JVM -Xxx is 4G,the 
> OutOfMemory will be happened.



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

[jira] [Commented] (FLUME-2752) Flume AvroSoucr will leak the memory and the OOM will be happened.

2015-07-29 Thread yinghua_zh (JIRA) 

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

yinghua_zh commented on FLUME-2752:
---

The avro soucr start method will start thread pool,but the NettyServer start 
failed,and the thread pool does not shutdown,Then the memory will be leaked,and 
the next 3 seconds will start thread pool,and the NettyServer start failed,and 
the thread pool does not shutdown,So the OutOfMemory will be happened.

> Flume AvroSoucr will leak the memory and the OOM will be happened.
> --
>
> Key: FLUME-2752
> URL: https://issues.apache.org/jira/browse/FLUME-2752
> Project: Flume
>  Issue Type: Bug
>  Components: Sinks+Sources
>Affects Versions: v1.6.0
>Reporter: yinghua_zh
>
> If the flume agent config the nonexist IP for the avro source,the exception 
> will be happened as follow:
> 2015-07-21 19:57:47,054 | ERROR | [lifecycleSupervisor-1-2] |  Unable to 
> start EventDrivenSourceRunner: { source:Avro source avro_source_21155: { 
> bindAddress: 51.196.27.32, port: 21155 } } - Exception follows.  | 
> org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:253)
> org.jboss.netty.channel.ChannelException: Failed to bind to: 
> /51.196.27.32:21155
>   at 
> org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:297)
>   at org.apache.avro.ipc.NettyServer.(NettyServer.java:106)
>   at org.apache.flume.source.AvroSource.start(AvroSource.java:294)
>   at 
> org.apache.flume.source.EventDrivenSourceRunner.start(EventDrivenSourceRunner.java:44)
>   at 
> org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:251)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.BindException: Cannot assign requested address
>   at sun.nio.ch.Net.bind0(Native Method)
>   at sun.nio.ch.Net.bind(Net.java:437)
>   at sun.nio.ch.Net.bind(Net.java:429)
>   at 
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
>   at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.bind(NioServerSocketPipelineSink.java:140)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleServerSocket(NioServerSocketPipelineSink.java:90)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:64)
>   at org.jboss.netty.channel.Channels.bind(Channels.java:569)
>   at 
> org.jboss.netty.channel.AbstractChannel.bind(AbstractChannel.java:189)
>   at 
> org.jboss.netty.bootstrap.ServerBootstrap$Binder.channelOpen(ServerBootstrap.java:342)
>   at org.jboss.netty.channel.Channels.fireChannelOpen(Channels.java:170)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketChannel.(NioServerSocketChannel.java:80)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:158)
>   at 
> org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:86)
>   at 
> org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:276)
> if the above exception happened for 2 hours,and the agent JVM -Xxx is 4G,the 
> OutOfMemory will be happened.



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

[jira] [Created] (FLUME-2752) Flume AvroSoucr will leak the memory and the OOM will be happened.

2015-07-29 Thread yinghua_zh (JIRA) 
yinghua_zh created FLUME-2752:
-

 Summary: Flume AvroSoucr will leak the memory and the OOM will be 
happened.
 Key: FLUME-2752
 URL: https://issues.apache.org/jira/browse/FLUME-2752
 Project: Flume
  Issue Type: Bug
  Components: Sinks+Sources
Affects Versions: v1.6.0
Reporter: yinghua_zh


If the flume agent config the nonexist IP for the avro source,the exception 
will be happened as follow:
2015-07-21 19:57:47,054 | ERROR | [lifecycleSupervisor-1-2] |  Unable to start 
EventDrivenSourceRunner: { source:Avro source avro_source_21155: { bindAddress: 
51.196.27.32, port: 21155 } } - Exception follows.  | 
org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:253)
org.jboss.netty.channel.ChannelException: Failed to bind to: /51.196.27.32:21155
at 
org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:297)
at org.apache.avro.ipc.NettyServer.(NettyServer.java:106)
at org.apache.flume.source.AvroSource.start(AvroSource.java:294)
at 
org.apache.flume.source.EventDrivenSourceRunner.start(EventDrivenSourceRunner.java:44)
at 
org.apache.flume.lifecycle.LifecycleSupervisor$MonitorRunnable.run(LifecycleSupervisor.java:251)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.BindException: Cannot assign requested address
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:437)
at sun.nio.ch.Net.bind(Net.java:429)
at 
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at 
org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.bind(NioServerSocketPipelineSink.java:140)
at 
org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleServerSocket(NioServerSocketPipelineSink.java:90)
at 
org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:64)
at org.jboss.netty.channel.Channels.bind(Channels.java:569)
at 
org.jboss.netty.channel.AbstractChannel.bind(AbstractChannel.java:189)
at 
org.jboss.netty.bootstrap.ServerBootstrap$Binder.channelOpen(ServerBootstrap.java:342)
at org.jboss.netty.channel.Channels.fireChannelOpen(Channels.java:170)
at 
org.jboss.netty.channel.socket.nio.NioServerSocketChannel.(NioServerSocketChannel.java:80)
at 
org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:158)
at 
org.jboss.netty.channel.socket.nio.NioServerSocketChannelFactory.newChannel(NioServerSocketChannelFactory.java:86)
at 
org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:276)


if the above exception happened for 2 hours,and the agent JVM -Xxx is 4G,the 
OutOfMemory will be happened.





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

[jira] [Commented] (FLUME-2660) Add documentation for EventValidator

2015-07-29 Thread Ashish Paliwal (JIRA) 

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

Ashish Paliwal commented on FLUME-2660:
---

The site is updated, already has this fix

> Add documentation for EventValidator
> 
>
> Key: FLUME-2660
> URL: https://issues.apache.org/jira/browse/FLUME-2660
> Project: Flume
>  Issue Type: Bug
>Affects Versions: v1.5.1
>Reporter: Hari Shreedharan
>Assignee: Ashish Paliwal
> Fix For: v1.7.0
>
> Attachments: FLUME-2660-0.patch, FLUME-2660-1.patch
>
>
> [~paliwalashish] - Assigning this to you. Please add docs for the 
> functionality you contributed in FLUME-2613



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

[jira] [Commented] (FLUME-2660) Add documentation for EventValidator

2015-07-29 Thread Hari Shreedharan (JIRA) 

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

Hari Shreedharan commented on FLUME-2660:
-

[~ashishpaliwal]/[~jrufus] - Could one of you apply the latest patch to the 
site? I believe Ashish applied the previous one (since this is really available 
in 1.6)

> Add documentation for EventValidator
> 
>
> Key: FLUME-2660
> URL: https://issues.apache.org/jira/browse/FLUME-2660
> Project: Flume
>  Issue Type: Bug
>Affects Versions: v1.5.1
>Reporter: Hari Shreedharan
>Assignee: Ashish Paliwal
> Fix For: v1.7.0
>
> Attachments: FLUME-2660-0.patch, FLUME-2660-1.patch
>
>
> [~paliwalashish] - Assigning this to you. Please add docs for the 
> functionality you contributed in FLUME-2613



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

[jira] [Commented] (FLUME-2660) Add documentation for EventValidator

2015-07-29 Thread Hudson (JIRA) 

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

Hudson commented on FLUME-2660:
---

UNSTABLE: Integrated in Flume-trunk-hbase-1 #116 (See 
[https://builds.apache.org/job/Flume-trunk-hbase-1/116/])
FLUME-2660. Add documentation for EventValidator. Fixed doc formatting issue 
(johnyrufus: 
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=fd32492ac7edf6b9b99cb6d2739739c37f4bc5a7)
* flume-ng-doc/sphinx/FlumeUserGuide.rst


> Add documentation for EventValidator
> 
>
> Key: FLUME-2660
> URL: https://issues.apache.org/jira/browse/FLUME-2660
> Project: Flume
>  Issue Type: Bug
>Affects Versions: v1.5.1
>Reporter: Hari Shreedharan
>Assignee: Ashish Paliwal
> Fix For: v1.7.0
>
> Attachments: FLUME-2660-0.patch, FLUME-2660-1.patch
>
>
> [~paliwalashish] - Assigning this to you. Please add docs for the 
> functionality you contributed in FLUME-2613



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

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

2015-07-29 Thread Apache Jenkins Server 
See

[jira] [Commented] (FLUME-2660) Add documentation for EventValidator

2015-07-29 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on FLUME-2660:


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

FLUME-2660. Add documentation for EventValidator. Fixed doc formatting issue

(Ashish Paliwal via Johny Rufus)


> Add documentation for EventValidator
> 
>
> Key: FLUME-2660
> URL: https://issues.apache.org/jira/browse/FLUME-2660
> Project: Flume
>  Issue Type: Bug
>Affects Versions: v1.5.1
>Reporter: Hari Shreedharan
>Assignee: Ashish Paliwal
> Fix For: v1.7.0
>
> Attachments: FLUME-2660-0.patch, FLUME-2660-1.patch
>
>
> [~paliwalashish] - Assigning this to you. Please add docs for the 
> functionality you contributed in FLUME-2613



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

[jira] [Commented] (FLUME-2660) Add documentation for EventValidator

2015-07-29 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on FLUME-2660:


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

FLUME-2660. Add documentation for EventValidator. Fixed doc formatting issue

(Ashish Paliwal via Johny Rufus)


> Add documentation for EventValidator
> 
>
> Key: FLUME-2660
> URL: https://issues.apache.org/jira/browse/FLUME-2660
> Project: Flume
>  Issue Type: Bug
>Affects Versions: v1.5.1
>Reporter: Hari Shreedharan
>Assignee: Ashish Paliwal
> Fix For: v1.7.0
>
> Attachments: FLUME-2660-0.patch, FLUME-2660-1.patch
>
>
> [~paliwalashish] - Assigning this to you. Please add docs for the 
> functionality you contributed in FLUME-2613



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

[jira] [Commented] (FLUME-2660) Add documentation for EventValidator

2015-07-29 Thread Johny Rufus (JIRA) 

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

Johny Rufus commented on FLUME-2660:


+1, Ran the -Psite and checked the UserGuide, the error is resolved, committing 

> Add documentation for EventValidator
> 
>
> Key: FLUME-2660
> URL: https://issues.apache.org/jira/browse/FLUME-2660
> Project: Flume
>  Issue Type: Bug
>Affects Versions: v1.5.1
>Reporter: Hari Shreedharan
>Assignee: Ashish Paliwal
> Fix For: v1.7.0
>
> Attachments: FLUME-2660-0.patch, FLUME-2660-1.patch
>
>
> [~paliwalashish] - Assigning this to you. Please add docs for the 
> functionality you contributed in FLUME-2613



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

[jira] [Commented] (FLUME-2660) Add documentation for EventValidator

2015-07-29 Thread Ashish Paliwal (JIRA) 

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

Ashish Paliwal commented on FLUME-2660:
---

[~jrufus] Fixed the build issue with the patch. Would be great if you can 
commit the same.

> Add documentation for EventValidator
> 
>
> Key: FLUME-2660
> URL: https://issues.apache.org/jira/browse/FLUME-2660
> Project: Flume
>  Issue Type: Bug
>Affects Versions: v1.5.1
>Reporter: Hari Shreedharan
>Assignee: Ashish Paliwal
> Fix For: v1.7.0
>
> Attachments: FLUME-2660-0.patch, FLUME-2660-1.patch
>
>
> [~paliwalashish] - Assigning this to you. Please add docs for the 
> functionality you contributed in FLUME-2613



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

[jira] [Updated] (FLUME-2660) Add documentation for EventValidator

2015-07-29 Thread Ashish Paliwal (JIRA) 

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

Ashish Paliwal updated FLUME-2660:
--
Attachment: FLUME-2660-1.patch

> Add documentation for EventValidator
> 
>
> Key: FLUME-2660
> URL: https://issues.apache.org/jira/browse/FLUME-2660
> Project: Flume
>  Issue Type: Bug
>Affects Versions: v1.5.1
>Reporter: Hari Shreedharan
>Assignee: Ashish Paliwal
> Fix For: v1.7.0
>
> Attachments: FLUME-2660-0.patch, FLUME-2660-1.patch
>
>
> [~paliwalashish] - Assigning this to you. Please add docs for the 
> functionality you contributed in FLUME-2613



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

[jira] [Reopened] (FLUME-2660) Add documentation for EventValidator

2015-07-29 Thread Ashish Paliwal (JIRA) 

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

Ashish Paliwal reopened FLUME-2660:
---

The patch has build issue, re opening

> Add documentation for EventValidator
> 
>
> Key: FLUME-2660
> URL: https://issues.apache.org/jira/browse/FLUME-2660
> Project: Flume
>  Issue Type: Bug
>Affects Versions: v1.5.1
>Reporter: Hari Shreedharan
>Assignee: Ashish Paliwal
> Fix For: v1.7.0
>
> Attachments: FLUME-2660-0.patch
>
>
> [~paliwalashish] - Assigning this to you. Please add docs for the 
> functionality you contributed in FLUME-2613



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

[jira] [Commented] (FLUME-2660) Add documentation for EventValidator

2015-07-29 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on FLUME-2660:


Commit 1693348 from [~paliwalashish] in branch 'site/trunk'
[ https://svn.apache.org/r1693348 ]

Updated docs for FLUME-2660, fixed build error

> Add documentation for EventValidator
> 
>
> Key: FLUME-2660
> URL: https://issues.apache.org/jira/browse/FLUME-2660
> Project: Flume
>  Issue Type: Bug
>Affects Versions: v1.5.1
>Reporter: Hari Shreedharan
>Assignee: Ashish Paliwal
> Fix For: v1.7.0
>
> Attachments: FLUME-2660-0.patch
>
>
> [~paliwalashish] - Assigning this to you. Please add docs for the 
> functionality you contributed in FLUME-2613



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

[jira] [Commented] (FLUME-2660) Add documentation for EventValidator

2015-07-29 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on FLUME-2660:


Commit 1693347 from [~paliwalashish] in branch 'site/trunk'
[ https://svn.apache.org/r1693347 ]

Updated docs for FLUME-2660, fixed the headline and commit error

> Add documentation for EventValidator
> 
>
> Key: FLUME-2660
> URL: https://issues.apache.org/jira/browse/FLUME-2660
> Project: Flume
>  Issue Type: Bug
>Affects Versions: v1.5.1
>Reporter: Hari Shreedharan
>Assignee: Ashish Paliwal
> Fix For: v1.7.0
>
> Attachments: FLUME-2660-0.patch
>
>
> [~paliwalashish] - Assigning this to you. Please add docs for the 
> functionality you contributed in FLUME-2613



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

[jira] [Commented] (FLUME-2660) Add documentation for EventValidator

2015-07-29 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on FLUME-2660:


Commit 1693341 from [~paliwalashish] in branch 'site/trunk'
[ https://svn.apache.org/r1693341 ]

Updated docs for FLUME-2660

> Add documentation for EventValidator
> 
>
> Key: FLUME-2660
> URL: https://issues.apache.org/jira/browse/FLUME-2660
> Project: Flume
>  Issue Type: Bug
>Affects Versions: v1.5.1
>Reporter: Hari Shreedharan
>Assignee: Ashish Paliwal
> Fix For: v1.7.0
>
> Attachments: FLUME-2660-0.patch
>
>
> [~paliwalashish] - Assigning this to you. Please add docs for the 
> functionality you contributed in FLUME-2613



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