Hi Stack,
Thanks for the response, I am trying to maintain an hourly count of messages
between two keys/entities: Sender->recipient E.g. a->b
There are multiple ways of modelling this, but one that seems to fit nicely is:
Row key = a
Col = b
Timestamp/version= e.g hour-of-day or hour-of-epoch
Hi All,
The HBase shell count command run on a table is giving a different count than
the custom map reduce row counter job ran on snapshot of same table.
This is a custom row counter written by us which is similar to HBase default
map reduce row counter, the only difference is that our job
Hello Alex. We don't have such an ability. Can you say what the use case is
because I at least am having trouble understanding why you would want to do
such a thing.
Thank you,
S
On Wed, Dec 13, 2017 at 2:07 PM, Alex Loffler wrote:
> Hi Folks,
>
> I am using the HBase’s
Thanks again.
I will try the steps you suggested. I will get back if I have any other
doubts.
On Mon, Dec 18, 2017 at 7:49 PM, A D wrote:
> That is correct.
>
> When you bring down a RM the other two will keep the cluster up and
> running and all the NMs will keep working with
That is correct.
When you bring down a RM the other two will keep the cluster up and
running and all the NMs will keep working with other two while the third
one is being upgrade.
On 12/18/2017 09:17 AM, Debraj Manna wrote:
> Thanks AD.
>
> When you say one at a time it means I should upgrade
Thanks AD.
When you say one at a time it means I should upgrade a ResourceManager node
and once it is fully upgraded and up, move to the next ResourceManager node?
On Mon, Dec 18, 2017 at 7:41 PM, A D wrote:
> I strongly recommend following
>
I strongly recommend following
http://hadoop.apache.org/docs/r2.6.5/hadoop-project-dist/hadoop-hdfs/HdfsRollingUpgrade.html
for rolling upgrade.
HBase is no different when it comes to rolling upgrade. There is no
special command that you need to execute. Below are the steps that I
would
I am having a cluster like below
- 3 Hbase Master (1 Active & 2 standby)
- 4 Region Servers
- 4 Data Nodes
- 1 Primary & 1 Secondary Name Node
- 3 Journal Node
- 4 Nodemanager
- 3 Resource Manager (1 Active & 2 standby)
Can someone let me know how can I plan a rolling