Flume, mail # user - Connection logs

Connection logs

Mohit Anchlia 2013-01-18, 18:09

Even though I am using a long lived connections recently what I am seeing
is that flume is logging this on every request. Previously that wasn't the
case.

13/01/17 14:00:07 INFO hdfs.BucketWriter: Creating
maprfs:///user/apuser/web-analytics-qdc/flume-snappy/2013/01/17/14/
pprddaaas30f.ie.intuit.net/web.1358460007783.snappy.tmp
13/01/17 14:02:53 INFO ipc.NettyServer: [id: 0x33238785, /10.101.0.6:6149=> /
10.101.3.160:41414] OPEN
13/01/17 14:02:53 INFO ipc.NettyServer: [id: 0x33238785, /10.101.0.6:6149=> /
10.101.3.160:41414] BOUND: /10.101.3.160:41414
13/01/17 14:02:53 INFO ipc.NettyServer: [id: 0x33238785, /10.101.0.6:6149=> /
10.101.3.160:41414] CONNECTED: /10.101.0.6:6149
13/01/17 14:02:53 INFO ipc.NettyServer: [id: 0x33238785, /10.101.0.6:6149:> /
10.101.3.160:41414] DISCONNECTED
13/01/17 14:02:53 INFO ipc.NettyServer: [id: 0x33238785, /10.101.0.6:6149:> /
10.101.3.160:41414] UNBOUND
13/01/17 14:02:53 INFO ipc.NettyServer: [id: 0x33238785, /10.101.0.6:6149:> /
10.101.3.160:41414] CLOSED
13/01/17 14:02:53 INFO ipc.NettyServer: Connection to
/10.101.0.6:6149disconnected.
13/01/17 14:02:54 INFO ipc.NettyServer: [id: 0x6ec5122f, /10.101.0.6:26334=> /
10.101.3.160:41414] OPEN
13/01/17 14:02:54 INFO ipc.NettyServer: [id: 0x6ec5122f, /10.101.0.6:26334=> /
10.101.3.160:41414] BOUND: /10.101.3.160:41414
13/01/17 14:02:54 INFO ipc.NettyServer: [id: 0x6ec5122f, /10.101.0.6:26334=> /
10.101.3.160:41414] CONNECTED: /10.101.0.6:26334
13/01/17 14:02:54 INFO ipc.NettyServer: [id: 0x6ec5122f, /10.101.0.6:26334:> /
10.101.3.160:41414] DISCONNECTED
13/01/17 14:02:54 INFO ipc.NettyServer: [id: 0x6ec5122f, /10.101.0.6:26334:> /
10.101.3.160:41414] UNBOUND
13/01/17 14:02:54 INFO ipc.NettyServer: [id: 0x6ec5122f, /10.101.0.6:26334:> /
10.101.3.160:41414] CLOSED
13/01/17 14:02:54 INFO ipc.NettyServer: Connection to
/10.101.0.6:26334disconnected.
13/01/17 14:02:59 INFO ipc.NettyServer: [id: 0x407e75d2, /10.101.0.6:32157=> /
10.101.3.160:41414] OPEN
13/01/17 14:02:59 INFO ipc.NettyServer: [id: 0x407e75d2, /10.101.0.6:32157=> /
10.101.3.160:41414] BOUND: /10.101.3.160:41414
13/01/17 14:02:59 INFO ipc.NettyServer: [id: 0x407e75d2, /10.101.0.6:32157=> /
10.101.3.160:41414] CONNECTED: /10.101.0.6:32157
13/01/17 14:02:59 INFO ipc.NettyServer: [id: 0x407e75d2, /10.101.0.6:32157:> /
10.101.3.160:41414] DISCONNECTED
13/01/17 14:02:59 INFO ipc.NettyServer: [id: 0x407e75d2, /10.101.0.6:32157:> /
10.101.3.160:41414] UNBOUND
13/01/17 14:02:59 INFO ipc.NettyServer: [id: 0x407e75d2, /10.101.0.6:32157:> /
10.101.3.160:41414] CLOSED
13/01/17 14:02:59 INFO ipc.NettyServer: Connection to
/10.101.0.6:32157disconnected.

Re: Connection logs

Mohit Anchlia 2013-01-18, 20:09

Never mind found the issue. It's related to our health checks.

On Fri, Jan 18, 2013 at 10:09 AM, Mohit Anchlia <[EMAIL PROTECTED]>wrote:

> Even though I am using a long lived connections recently what I am seeing
> is that flume is logging this on every request. Previously that wasn't the
> case.
>
> 13/01/17 14:00:07 INFO hdfs.BucketWriter: Creating
> maprfs:///user/apuser/web-analytics-qdc/flume-snappy/2013/01/17/14/
> pprddaaas30f.ie.intuit.net/web.1358460007783.snappy.tmp
> 13/01/17 14:02:53 INFO ipc.NettyServer: [id: 0x33238785, /10.101.0.6:6149=> /
> 10.101.3.160:41414] OPEN
> 13/01/17 14:02:53 INFO ipc.NettyServer: [id: 0x33238785, /10.101.0.6:6149=> /
> 10.101.3.160:41414] BOUND: /10.101.3.160:41414
> 13/01/17 14:02:53 INFO ipc.NettyServer: [id: 0x33238785, /10.101.0.6:6149=> /
> 10.101.3.160:41414] CONNECTED: /10.101.0.6:6149
> 13/01/17 14:02:53 INFO ipc.NettyServer: [id: 0x33238785, /10.101.0.6:6149:> /
> 10.101.3.160:41414] DISCONNECTED
> 13/01/17 14:02:53 INFO ipc.NettyServer: [id: 0x33238785, /10.101.0.6:6149:> /
> 10.101.3.160:41414] UNBOUND
> 13/01/17 14:02:53 INFO ipc.NettyServer: [id: 0x33238785, /10.101.0.6:6149:> /
> 10.101.3.160:41414] CLOSED
> 13/01/17 14:02:53 INFO ipc.NettyServer: Connection to /10.101.0.6:6149disconnected.
> 13/01/17 14:02:54 INFO ipc.NettyServer: [id: 0x6ec5122f, /10.101.0.6:26334=> /
> 10.101.3.160:41414] OPEN
> 13/01/17 14:02:54 INFO ipc.NettyServer: [id: 0x6ec5122f, /10.101.0.6:26334=> /
> 10.101.3.160:41414] BOUND: /10.101.3.160:41414
> 13/01/17 14:02:54 INFO ipc.NettyServer: [id: 0x6ec5122f, /10.101.0.6:26334=> /
> 10.101.3.160:41414] CONNECTED: /10.101.0.6:26334
> 13/01/17 14:02:54 INFO ipc.NettyServer: [id: 0x6ec5122f, /10.101.0.6:26334:> /
> 10.101.3.160:41414] DISCONNECTED
> 13/01/17 14:02:54 INFO ipc.NettyServer: [id: 0x6ec5122f, /10.101.0.6:26334:> /
> 10.101.3.160:41414] UNBOUND
> 13/01/17 14:02:54 INFO ipc.NettyServer: [id: 0x6ec5122f, /10.101.0.6:26334:> /
> 10.101.3.160:41414] CLOSED
> 13/01/17 14:02:54 INFO ipc.NettyServer: Connection to /10.101.0.6:26334disconnected.
> 13/01/17 14:02:59 INFO ipc.NettyServer: [id: 0x407e75d2, /10.101.0.6:32157=> /
> 10.101.3.160:41414] OPEN
> 13/01/17 14:02:59 INFO ipc.NettyServer: [id: 0x407e75d2, /10.101.0.6:32157=> /
> 10.101.3.160:41414] BOUND: /10.101.3.160:41414
> 13/01/17 14:02:59 INFO ipc.NettyServer: [id: 0x407e75d2, /10.101.0.6:32157=> /
> 10.101.3.160:41414] CONNECTED: /10.101.0.6:32157
> 13/01/17 14:02:59 INFO ipc.NettyServer: [id: 0x407e75d2, /10.101.0.6:32157:> /
> 10.101.3.160:41414] DISCONNECTED
> 13/01/17 14:02:59 INFO ipc.NettyServer: [id: 0x407e75d2, /10.101.0.6:32157:> /
> 10.101.3.160:41414] UNBOUND
> 13/01/17 14:02:59 INFO ipc.NettyServer: [id: 0x407e75d2, /10.101.0.6:32157:> /
> 10.101.3.160:41414] CLOSED
> 13/01/17 14:02:59 INFO ipc.NettyServer: Connection to /10.101.0.6:32157disconnected.
>