> Date: Fri, 16 Jul 2010 13:02:15 -0700
> Subject: Re: Row level locking?
> From: [email protected]
> To: [email protected]
> CC: [email protected]
>
> HTable.close does very little:
>
> public void close() throws IOException{
> flushCommits();
> }
>
>
> None of which involves row locks.
>
> One thing to watch out for is to remember to close your scanners -
> they continue to use server-side resources until you close them or 60
> seconds passes and they get timed out. Also be very wary of using any
> of the explicit row locking calls, they are generally trouble for more
> or less everyone. There was a proposal to remove them, but I don't
> think that went through.
>
>
Thanks Ryan.
This may be more of the issue that they are seeing.
I have to do a code review on their code to see what they are doing.
In batch (map/reduce) this isn't much of an issue.
In a more transactional use case, this can become an issue.
(Batch you're usually using a scanner at the start of the m/r and then
processing the data...)
_________________________________________________________________
The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail.
http://www.windowslive.com/campaign/thenewbusy?tile=multiaccount&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4
