> > > On 2 Sep 2017, at 12:55, Ted Yu wrote:
> > >
> > > Did you use graceful_stop.sh before the restart ?
> > >
> > >> On Sat, Sep 2, 2017 at 1:12 AM, Rob Verkuylen
> > wrote:
> > >>
> > >> On CDH5.12 with HBase 1.2,
On CDH5.12 with HBase 1.2, I'm experiencing an issue I thought was long
solved. The regions are all assigned to a single regionserver on a restart
of hbase though cloudera manager.
The Hbase book 9,1.1 states that
'hbase.master.wait.on.regionservers.mintostart'
should be the proper setting to hand
Aug 2016, at 20:01, Ted Yu wrote:
> >>
> >> Please verify that your 0.94 cluster is configured with hfile v2.
> >> Config hfile.format.version should have value of 2.
> >>
> >> To obtain region boundaries, you can use 'describe' hbase shell
> >
> > System.err.println("To import data exported from HBase 0.94, use");
> >
> > System.err.println(" -Dhbase.import.version=0.94");
> >
> > FYI
> >
> > On Sun, Aug 14, 2016 at 12:09 AM, Rob Verkuylen
> wrote:
>
We're recovering from a crash of hbase-0.94.6 where the master refuses to
come up, while hdfs is fine. Why this happened exactly is something we're
looking into.
In the meantime we're looking to migrate as fast as possible to another
cluster running hbase1.2.
Since we cannot use the default impor
ready at your disposal for re-try if
> something fails?
> Sounds faster to me anyway.
>
> On May 30, 2013, at 10:52 PM, Rob Verkuylen wrote:
>
>>
>> On May 30, 2013, at 4:51, Stack wrote:
>>
>>> Triggering a major compaction does not alter the overall 217.5
On May 30, 2013, at 4:51, Stack wrote:
> Triggering a major compaction does not alter the overall 217.5GB size?
A major compaction reduces the size from the original 219GB to the 217,5GB, so
barely a reduction.
80% of the region sizes are 1,4GB before and after. I haven't merged the
smaller
Just to add from my experiences:
Yes hotspotting is bad, but so are devops headaches. A reasonable machine
can handle 3-4000 puts a second with ease, and a simple timerange scan can
give you the records you need. I have my doubts you will be hitting these
amounts anytime soon. A simple setup will
t; >>
> >> http://hbase.apache.org/book.html#regions.arch
> >> 8.7.5.4. KeyValue
> >>
> >>
> >>
> >> The timestamp is an attribute of the KeyValue, but unless you perform a
> >> restriction using start/stop row it have to proces
I'm trying to find a definitive answer to the question if scans on
timerange alone will scale when you use uniformly distributed keys like
UUIDs.
Since the keys are randomly generated that would mean the keys will be
spread out over all RegionServers, Regions and HFiles. In theory, assuming
enough
10 matches
Mail list logo
