hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Helmling <ghelml...@gmail.com>
Subject Re: Coprocessor Client Blocking
Date Wed, 22 Jan 2014 00:57:42 GMT
Yes, the pre/post method calls for the Observer hooks (RegionObserver for
postPut()) are executed synchronously on the RPC calling path.  So the
RegionServer will not return the response to the client until your
postPut() method has returned.  In general, this means that for best
performance you should only load Observers that you need, and any Observers
you write should do their processing as efficiently as possible.

On Tue, Jan 21, 2014 at 4:32 PM, Pradeep Gollakota <pradeepg26@gmail.com>wrote:

> Hi All,
> In the blog describing the coprocessor there was sequence diagram walking
> through the lifecycle of a Get.
> https://blogs.apache.org/hbase/mediaresource/60b135e5-04c6-4197-b262-e7cd08de784b
> I'm wondering if the lifecycle of a Put follows the same sequence.
> Specifically for my use case, I'm doing some processing using a
> RegionObserver in the postPut() method. Does the client wait until the
> postPut() is executed? When is the control returned to the client in a Put?
> Thanks!

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