Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # user >> Coprocessors - failure


Copy link to this message
-
Re: Coprocessors - failure
Thanks Ted.
Basically it's recommended to avoid using RPC calls when writing from
table A to B, having the region in the same RegionServer. There i will
exclude network failures. Am i right?
On 08/21/2013 11:02 AM, Ted Yu wrote:
> See http://search-hadoop.com/m/XtAi5Fogw32
>
>
> On Wed, Aug 21, 2013 at 6:56 AM, Federico Gaule <[EMAIL PROTECTED]> wrote:
>
>> Table A and B are within the same HBase cluster. Can't guarantee they are
>> in the same physical machine.
>>
>> Thanks
>>
>> On 08/21/2013 10:54 AM, Ted Yu wrote:
>>
>>> Are tables A and B colocated ?
>>> Meaning, is your coprocessor making an RPC call to another server ?
>>>
>>> Cheers
>>>
>>>
>>> On Wed, Aug 21, 2013 at 6:00 AM, Federico Gaule <[EMAIL PROTECTED]>
>>> wrote:
>>>
>>>   Hi everyone,
>>>> Let's say, I have a table(A) where every time I write a coprocessor,
>>>> hooked to postPut, writes in other table (B). I can't find anywhere what
>>>> happen if the coprocessor fails or can't connect to B
>>>> Does the client get aware of that?  In case it doesn't, how can i get
>>>> noticed about the failure?
>>>> Does the Put get rolled back (I think coprocessors works outside row
>>>> transaction) ?
>>>>
>>>> Thanks!
>>>> Federico
>>>>
>>>>
>>>>
>>>>
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB