flume-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From terreyshih <terreys...@gmail.com>
Subject runner.backoffs and runner.backoffs.consecutive ? related to ChannelFullException ?
Date Tue, 13 Jan 2015 18:19:36 GMT
anybody and shed some light on this ? thx

> On Jan 12, 2015, at 11:28 PM, terreyshih <terreyshih@gmail.com> wrote:
> 
> Hi,
> 
> What do the values runner.backoffs.consecutive and runner.backoffs value mean ? I get
ChannelFullException shortly afterwards.
> 
> thanks,
> -Terrey
> 
> 
> 
> 2015-01-10 02:05:14,500 DEBUG [lifecycleSupervisor-1-1] [o.a.f.l.LifecycleSupervisor.run:214]
- checking process:SinkRunner: { policy:org.apache.flume.sink.DefaultSinkProcessor@63b8dba5
counterGroup:{ name:null counters:{runner.backoffs.consecutive=8, runner.backoffs=2120} }
} supervisoree:{ status:{ lastSeen:1420884311499 lastSeenState:START desiredState:START firstSeen:1420869500254
failures:0 discard:false error:false } policy:org.apache.flume.lifecycle.LifecycleSupervisor$SupervisorPolicy$AlwaysRestartPolicy@2e60639b
}
> 
> 
> 
> Caused by: org.apache.flume.ChannelFullException: Space for commit to queue couldn't
be acquired. Sinks are likely not keeping up with sources, or the buffer size is too tight


Mime
View raw message