hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Esteban Gutierrez <este...@cloudera.com>
Subject Re: Upgrading CDH from 5.7 to 5.13 from Community Edition
Date Fri, 08 Dec 2017 16:14:06 GMT
Hello Debraj,

Vendor specific questions should be addressed via their mailing lists or
community sites. For CDH specific questions you should visit:
http://community.cloudera.com

Thanks,
Esteban.



--
Cloudera, Inc.


On Fri, Dec 8, 2017 at 9:00 AM, Debraj Manna <subharaj.manna@gmail.com>
wrote:

> Hi
>
> This is my first post in this mailing list. I am not sure if this is the
> right place to ask this question
>
> I don't have any enterprise license.
>
> I am having a cluster like below
>
>
>    1. 3 Hbase Master (1 Active & 2 standby)
>    2. 4 Region Servers
>    3. 4 Data Nodes
>    4. 1 Primary & 1 Secondary Name Node
>    5. 3 Journal Node
>    6. 4 Nodemanager
>    7. 3 Resource Manager (1 Active & 2 standby)
>
> The underlying versions of hadoop & hbase components have not changed in
> 5.7 & 5.13. So can I just upgrade the services in any random order? For
> example let's say I have upgraded the Secondary Name Node and some data
> node to the latest 5.13. Will the updated node will be able to talk with
> the old 5.7 ? Is the latest 5.13 fully backward compatible with 5.7?
> Cluster downtime is not an issue but eventually when all the node is
> updated will the cluster be fine.
>
> The above question may sound little weird but in short I am asking this
> because the legacy set-up in which I am working right now does not have any
> centralized mechanism to control upgrade like secondary NN first then
> primary & so on.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message