hadoop-common-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stas Oskin <stas.os...@gmail.com>
Subject Re: InputStream.open() efficiency
Date Wed, 27 May 2009 07:40:26 GMT
Hi.

Thanks for the advice.

Regards.

2009/5/26 Raghu Angadi <rangadi@yahoo-inc.com>

> Stas Oskin wrote:
>
>> Hi.
>>
>> Thanks for the answer.
>>
>> Would up to 5 minute of handlers cause any issues?
>>
>
> 5 min should not cause any issues..
>
>  And same about writing?
>>
>
> writing is not affected by the couple of issues I mentioned. Writing over a
> long time should work as well as writing over shorter time.
>
> Raghu.
>
>
>  Regards.
>>
>> 2009/5/26 Raghu Angadi <rangadi@yahoo-inc.com>
>>
>>  'in.seek(); in.read()' is certainly better than,
>>> 'in = fs.open(); in.seek(); in.read()'
>>>
>>> The difference is is exactly one open() call. So you would save an RPC to
>>> NameNode.
>>>
>>> There are couple of issues that affect apps that keep the handlers open
>>> very long time (many hours to days).. but those will be fixed soon.
>>>
>>> Raghu.
>>>
>>>
>>> Stas Oskin wrote:
>>>
>>>  Hi.
>>>>
>>>> I'm looking to find out, how the InputStream.open() + skip(), compares
>>>> to
>>>> keeping a handle of InputStream() and just seeking the position.
>>>>
>>>> Has anyone compared these approaches, and can advice on their speed?
>>>>
>>>> Regards.
>>>>
>>>>
>>>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message