Hi,
Please look into the following issue
Scenario:
1) Created an AWS EMR HBASE cluster with 1 Master node and 2 Core(Slave)
nodes
2) Created HBase table with 20 regions auto split across the 2 Core nodes
3) I downscaled my cluster to 1 Core node
4) The table doesn't seem to work
Questions:
Is it
>
> Which hbase release are you using ?
>
> Please pastebin relevant master log / region server log.
>
> Thanks
>
> > On Feb 9, 2017, at 3:50 AM, Devi Sunil Kumar Shegu <
> sunil143d...@gmail.com> wrote:
> >
> > Hi,
> >
> > Please look into t
;
> I'm able to successfully scale my HBase clusters up and down (core and
> task) on EMR. Can you please provide the logs in pastebin so that we can
> help?
>
> On Feb 10, 2017 12:10 AM, "Devi Sunil Kumar Shegu" >
> wrote:
>
> Hey Ted,
>
> Thanks for
Hi ,
1) I have 1 Master node and 1 Slave node
2) Created a table with the below query
create 'my_table', 'u', { NUMREGIONS => 16, SPLITALGO => 'HexStringSplit'}
3) All the regions are in the single slave Node
4) Here is the table description
{NAME => 'u', BLOOMFILTER => 'ROW', VERSIONS => '1', IN
for reads, consider using BucketCache.
Cheers
> On Feb 10, 2017, at 2:22 AM, Devi Sunil Kumar Shegu <
sunil143d...@gmail.com> wrote:
>
> Hi ,
>
> 1) I have 1 Master node and 1 Slave node
> 2) Created a table with the below query
> create 'my_table', '
Hi,
Scan and get are yielding different results for the same column even when
versioning is disabled.
Thanks in advance and please check the details below
Description of the table:
{NAME => 'u', BLOOMFILTER => 'ROW', VERSIONS => '1', IN_MEMORY => 'false',
KEEP_DELETED_CELLS => 'FALSE', DATA_BLO
