Re: question on snapshot and export utility
Thanks Vlad. I will take a look. Antonio. On Wed, Sep 5, 2018 at 12:15 PM Vladimir Rodionov wrote: > No, it is not, to my best knowledge. ExportSnapshot just move files to new > destination using M/R job. > But, you can do the custom filtering yourself. Look at ExportSnapshot > implementation. All you need is a new > Mapper which does required filtering of a HFile before moving data to a > destination. > > -Vlad > > On Wed, Sep 5, 2018 at 10:51 AM Antonio Si wrote: > > > Hi, > > > > When taking a snapshot or running the export utility, is it possible to > > specify a condition or filter on some columns so that only rows that > > satisfy the condition will be included in the snapshot or exported? > > > > Thanks. > > > > Antonio. > > >
Re: Extremely high CPU usage after upgrading to Hbase 1.4.4
>From the stack trace, ColumnPrefixFilter is used during scan. Can you illustrate how various filters are formed thru FilterListWithOR ? It would be easier for other people to reproduce the problem given your query pattern. Cheers On Thu, Sep 6, 2018 at 11:43 AM Srinidhi Muppalla wrote: > Hi Vlad, > > Thank you for the suggestion. I recreated the issue and attached the stack > traces I took. Let me know if there’s any other info I can provide. We > narrowed the issue down to occurring when upgrading from 1.3.0 to any 1.4.x > version. > > Thanks, > Srinidhi > > On 9/4/18, 8:19 PM, "Vladimir Rodionov" wrote: > > Hi, Srinidhi > > Next time you will see this issue, take jstack of a RS several times > in a > row. W/o stack traces it is hard > to tell what was going on with your cluster after upgrade. > > -Vlad > > > > On Tue, Sep 4, 2018 at 3:50 PM Srinidhi Muppalla > > wrote: > > > Hello all, > > > > We are currently running Hbase 1.3.0 on an EMR cluster running EMR > 5.5.0. > > Recently, we attempted to upgrade our cluster to using Hbase 1.4.4 > (along > > with upgrading our EMR cluster to 5.16). After upgrading, the CPU > usage for > > all of our region servers spiked up to 90%. The load_one for all of > our > > servers spiked from roughly 1-2 to 10 threads. After upgrading, the > number > > of operations to the cluster hasn’t increased. After giving the > cluster a > > few hours, we had to revert the upgrade. From the logs, we are > unable to > > tell what is occupying the CPU resources. Is this a known issue with > 1.4.4? > > Any guidance or ideas for debugging the cause would be greatly > > appreciated. What are the best steps for debugging CPU usage? > > > > Thank you, > > Srinidhi > > > > >
Re: Extremely high CPU usage after upgrading to Hbase 1.4.4
Hi Vlad, Thank you for the suggestion. I recreated the issue and attached the stack traces I took. Let me know if there’s any other info I can provide. We narrowed the issue down to occurring when upgrading from 1.3.0 to any 1.4.x version. Thanks, Srinidhi On 9/4/18, 8:19 PM, "Vladimir Rodionov" wrote: Hi, Srinidhi Next time you will see this issue, take jstack of a RS several times in a row. W/o stack traces it is hard to tell what was going on with your cluster after upgrade. -Vlad On Tue, Sep 4, 2018 at 3:50 PM Srinidhi Muppalla wrote: > Hello all, > > We are currently running Hbase 1.3.0 on an EMR cluster running EMR 5.5.0. > Recently, we attempted to upgrade our cluster to using Hbase 1.4.4 (along > with upgrading our EMR cluster to 5.16). After upgrading, the CPU usage for > all of our region servers spiked up to 90%. The load_one for all of our > servers spiked from roughly 1-2 to 10 threads. After upgrading, the number > of operations to the cluster hasn’t increased. After giving the cluster a > few hours, we had to revert the upgrade. From the logs, we are unable to > tell what is occupying the CPU resources. Is this a known issue with 1.4.4? > Any guidance or ideas for debugging the cause would be greatly > appreciated. What are the best steps for debugging CPU usage? > > Thank you, > Srinidhi > <>
