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 >> increment-related bug Was: HBASE-7114 Increment does not extend Mutation but probably should


Copy link to this message
-
Re: increment-related bug Was: HBASE-7114 Increment does not extend Mutation but probably should
We ran 150gig of Increment objects. When we compared the expected, we
had a lot more than expected.
We are using 0.94.3.
I will run this qa test again tomorrow with logging of HTable turned
on debug so I can track retries.
Sent from my iPhone

On 26 בינו 2013, at 18:56, Ted Yu <[EMAIL PROTECTED]> wrote:

> Asaf:
> Were you referring to HBASE-6291: Don't retry increments on an invalid cell
> ?
> That was fixed in 0.94.2
>
> Or maybe: HBASE-6195 Increment data will be lost when the memstore is
> flushed
> The above was fixed in 0.94.1
>
> Cheers
>
> On Sat, Jan 26, 2013 at 8:40 AM, Asaf Mesika <[EMAIL PROTECTED]> wrote:
>
>> The all counters is on the same row?
>>
>> By the way, did you guys handle the hbase bug that when an increment is
>> sent to region server and fails it still does it but throws an exception to
>> the client which causes it to do that increment again?
>>
>>
>> Sent from my iPhone
>>
>> On 26 בינו 2013, at 17:32, Amit Sela <[EMAIL PROTECTED]> wrote:
>>
>> Well, I increment counters where the row key is a keyword and the qualifier
>> is a country code, and in the post increment region observer I increment an
>> "all countries" aggregative counter. These counters are divided to families
>> such as daily, weekly, hourly etc.
>> So I get the family map to know which aggregative counter should I
>> increment, then I piggyback onto the Result the "all countries" current
>> count.
>> On Jan 26, 2013 2:39 AM, "Ted Yu" <[EMAIL PROTECTED]> wrote:
>>
>> Amit:
>>
>> Can you tell us what operation you perform on the returned family map ?
>>
>>
>> Thanks
>>
>>
>> On Thu, Jan 24, 2013 at 3:37 AM, Amit Sela <[EMAIL PROTECTED]> wrote:
>>
>>
>> I'm using Increment.getFamilyMap in a postIncrement Observer.
>>
>> I'm running with HBase 0.94.2.
>>
>>
>> Amit.
>>
>>
>> On Thu, Jan 24, 2013 at 4:23 AM, lars hofhansl <[EMAIL PROTECTED]> wrote:
>>
>>
>> The reason was that Increment was serialized differently (compared to
>>
>> all
>>
>> other mutations).
>>
>> In trunk that is no longer an issue, since the serialization logic is
>>
>> no
>>
>> longer part of the object to be serialized.
>>
>>
>>
>> -- Lars
>>
>>
>>
>>
>> ________________________________
>>
>> From: Ted Yu <[EMAIL PROTECTED]>
>>
>> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
>>
>> Sent: Wednesday, January 23, 2013 10:25 AM
>>
>> Subject: HBASE-7114 Increment does not extend Mutation but probably
>>
>> should
>>
>>
>> Hi,
>>
>> I want to get opinion on whether we should proceed with HBASE-7114
>>
>> 'Increment does not extend Mutation but probably should' in trunk.
>>
>>
>> Is anyone using Increment.setWriteToWAL or Increment.getFamilyMap ?
>>
>> For Increment.setWriteToWAL, are you using the Increment returned ?
>>
>>
>> Your feedback would be appreciated.
>>
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