avro-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yang <teddyyyy...@gmail.com>
Subject Re: timeout on cable lost ?
Date Mon, 31 Oct 2011 17:18:01 GMT
thanks James.

"because no timeout is used....",  is it possible to specify a timeout
for the current nettyTransceiver code? the normal SO_TIMEOUT applies
to Socket, but it seems NettyTransceiver does not take a Socket input
in constructor.

Yang

On Mon, Oct 31, 2011 at 10:10 AM, James Baldassari
<jbaldassari@gmail.com> wrote:
> Hi Yang,
>
> NettyTransceiver tries to automatically reconnect if the connection is
> lost.  Sometimes it gets stuck because no timeout is used on the connection,
> as you mentioned.  Please see this issue for a patch:
>
> https://issues.apache.org/jira/browse/AVRO-943
>
> -James
>
>
> On Mon, Oct 31, 2011 at 1:07 PM, Yang <teddyyyy123@gmail.com> wrote:
>>
>> it looks
>>
>> NettyTransceiver.getChannel().getChannelConfig().setTimeoutMillis()
>> could be a possible approach?
>>
>>
>>
>> On Mon, Oct 31, 2011 at 9:41 AM, Yang <teddyyyy123@gmail.com> wrote:
>> > this is more of a problem on TCP itself: if I have a TCP connection
>> > established, then
>> > I pull out the network cable, the TCP connection is still on, as soon
>> > as I re-connect the cable.
>> >
>> > in the case of Avro RPC call, if I pull out the cable, the RPC just
>> > blocks, without throwing an exception.
>> > I see https://issues.apache.org/jira/browse/FLUME-313   addressing
>> > this for HTTP transceiver,
>> > is there a similar patch for NettyTransceiver?
>> >
>> > Thanks
>> > Yang
>> >
>
>

Mime
View raw message