FAQ
Hi Ben,

You do not need to set any special configurations for the embedded
postgres, though you may want to tune performance-related parameters in a
production environment.

The postgres driver is now automatically handled by CM for all hive configs
managed by CM. That means hue, hive metastore server, impala, and hive
configs updated the command Deploy Client Configs. Note that if you
download client configs, then you'll need to make sure your machine has the
driver and it is added properly to the classpath. Also note that oracle and
mysql jars have special instructions, which are documented on the pages for
setting up those databases.

As you guessed, the beeswax safety valve information should be removed.

Thanks,
Darren

On Thu, Feb 28, 2013 at 8:36 AM, Benjamin Kim wrote:

bc,

I have general question.

Now that by default, the Hive metastore will be housed in the embedded
PostgreSQL DB. Do we still need to set configurations based on the
information contained at the link below or is it set for us?

https://ccp.cloudera.com/**display/ENT4DOC/Installing+**
and+Configuring+an+External+**PostgreSQL+Database<https://ccp.cloudera.com/display/ENT4DOC/Installing+and+Configuring+an+External+PostgreSQL+Database>

I assume that the PostgreSQL driver file is already provided so that
copying it to /usr/lib/hive/lib is not necessary. In addition, the custom
beeswax configurations shown below are no longer needed in the Hue
Service Configuration Safety Valve.

[beeswax]
hive_home_dir=/usr/lib/hive
hive_conf_dir=/etc/hive/conf

Thanks,
Ben
On Tuesday, February 26, 2013 8:02:29 AM UTC-8, bc Wong wrote:

On behalf of the Cloudera Manager team, I'm proud to announce the general
availability of Cloudera Manager 4.5<https://ccp.cloudera.com/display/SUPPORT/Cloudera+Manager+Downloads>.
This release packs tons of new features and improvements, including:

- *Easy CDH upgrade* with a new packaging format called "parcel".
Rather than manually upgrading the CDH packages across your cluster, you
can now download, distribute and activate a new CDH version all from within
Cloudera Manager.

- *Improved configuration management for role instances*. You can now
group an arbitrary set of roles instances (of the same type, e.g.
DataNodes) together and manage their configuration as a unit. Called "Role
Configuration Groups", this feature simplifies configuring groups of roles
that need to be configured differently, for example when running on nodes
with heterogeneous hardware.
*
*
- *Improved role to host assignment with Host Templates*. A host
template defines a set of role configurations that can be applied to new
hosts. This simplifies the process of adding hosts and instantiating the
roles that should run on those hosts.

- *AWS installation wizard* can bring up your entire from scratch
(including EC2 instance creation), and optimize settings for the AWS
environment. This is an excellent way to try out a fully functional CDH
cluster managed by Cloudera Manager, although it is not intended for
long-running production use.

- *Support for Hive*, including the automatic creation of the Hive
Metastore database. It also supports running the Hive Metastore Server and
HiveServer2. If you have configured Hue or Impala, then upgrading to
Cloudera Manager 4.5 will automatically create new Hive service(s), migrate
the existing Hive related configuration over, and link Hue and Impala to
the new Hive service(s).

- *Resource management* enables sharing multiple workloads (such as
MapReduce and Impala) on the same cluster, by partitioning cluster
resources (CPU, memory) across different services.

- *Removal of 50 node limit*. Cloudera Manager Free Edition no long
limits the number of nodes it can manage.

- *General usability and user interface improvements*.

In addition, the Cloudera Manager 4.5 *Enterprise Edition* has added:

- *Rolling restart* of services with zero/minimal downtime, used for
effecting configuration changes, or upgrading your services (via parcels).
You can do a rolling restart of an entire service, or just of certain
roles. If you have enabled HDFS High Availability, you can also do a
rolling restart on the entire cluster.

- *Backup and Disaster Recovery* is an independently-licensed feature
that replicates HDFS data files, and Hive Metastore and data files between
clusters managed by different Cloudera Manager instances.

- *HBase monitoring improvements* bring new health checks, metrics,
domain specific events (such as compactions and splits), periodic region
liveness checks (HBase canary) and data integrity checks (hbck).

- *Advanced charting*. The host and service pages show a lot more
charts on a lot more metrics, which provide useful tools for performance
and diagnostics. In addition, you can build your own charts and dashboards
with access to the raw metrics data using a new time-series query language,
called tsquery.

- *Proactive support* with automated cluster statistics collection.
Periodic diagnostics gathering (enabled by default) allows Cloudera Support
to discover any potential issues from the collected configuration files,
log files, and other environmental information.

- *SNMP alerts* enables easier integration with IT management tools.

For more details on new features, please see the full release notes: [Free
Edition<https://ccp.cloudera.com/display/FREE45DOC/New+Features+in+Cloudera+Manager+Free+Edition+4>]
[Enterprise Edition<https://ccp.cloudera.com/display/ENT45DOC/New+Features+in+Cloudera+Manager+4>
]

Getting Cloudera Manager 4.5:

- Download at https://ccp.cloudera.com/**display/SUPPORT/Cloudera+**
Manager+Downloads<https://ccp.cloudera.com/display/SUPPORT/Cloudera+Manager+Downloads>
- Installation guide: https://ccp.cloudera.**com/display/FREE45DOC/**
Cloudera+Manager+Free+Edition+**Installation+Guide<https://ccp.cloudera.com/display/FREE45DOC/Cloudera+Manager+Free+Edition+Installation+Guide>
- Feedback and support: scm-...@cloudera.**org <https://groups.google.
**com/a/cloudera.org/forum/?hl=**en&fromgroups#!forum/scm-users<https://groups.google.com/a/cloudera.org/forum/?hl=en&fromgroups#!forum/scm-users>
**>

We look forward to your feedback. Lastly, we'd like to thank everybody
who tried out the 4.5 Beta. Your support makes Cloudera Manager a better
product.

Cheers,
bc

--
Thanks,
Darren

Search Discussions

  • Philippe Marseille at Feb 28, 2013 at 7:11 pm
    We're using MySql for the metastore

    The Hive config was migrated successfully but for some reasons, the service
    will report an error if the "Metadata Server" role is not configured and
    running...

    Is this normal? I don't need this service...
    On Thursday, 28 February 2013 13:17:28 UTC-5, Darren Lo wrote:

    Hi Ben,

    You do not need to set any special configurations for the embedded
    postgres, though you may want to tune performance-related parameters in a
    production environment.

    The postgres driver is now automatically handled by CM for all hive
    configs managed by CM. That means hue, hive metastore server, impala, and
    hive configs updated the command Deploy Client Configs. Note that if you
    download client configs, then you'll need to make sure your machine has the
    driver and it is added properly to the classpath. Also note that oracle and
    mysql jars have special instructions, which are documented on the pages for
    setting up those databases.

    As you guessed, the beeswax safety valve information should be removed.

    Thanks,
    Darren


    On Thu, Feb 28, 2013 at 8:36 AM, Benjamin Kim <bbui...@gmail.com<javascript:>
    wrote:
    bc,

    I have general question.

    Now that by default, the Hive metastore will be housed in the embedded
    PostgreSQL DB. Do we still need to set configurations based on the
    information contained at the link below or is it set for us?

    https://ccp.cloudera.com/**display/ENT4DOC/Installing+**
    and+Configuring+an+External+**PostgreSQL+Database<https://ccp.cloudera.com/display/ENT4DOC/Installing+and+Configuring+an+External+PostgreSQL+Database>

    I assume that the PostgreSQL driver file is already provided so that
    copying it to /usr/lib/hive/lib is not necessary. In addition, the custom
    beeswax configurations shown below are no longer needed in the Hue
    Service Configuration Safety Valve.

    [beeswax]
    hive_home_dir=/usr/lib/hive
    hive_conf_dir=/etc/hive/conf

    Thanks,
    Ben
    On Tuesday, February 26, 2013 8:02:29 AM UTC-8, bc Wong wrote:

    On behalf of the Cloudera Manager team, I'm proud to announce the
    general availability of Cloudera Manager 4.5<https://ccp.cloudera.com/display/SUPPORT/Cloudera+Manager+Downloads>.
    This release packs tons of new features and improvements, including:

    - *Easy CDH upgrade* with a new packaging format called "parcel".
    Rather than manually upgrading the CDH packages across your cluster, you
    can now download, distribute and activate a new CDH version all from within
    Cloudera Manager.

    - *Improved configuration management for role instances*. You can
    now group an arbitrary set of roles instances (of the same type, e.g.
    DataNodes) together and manage their configuration as a unit. Called "Role
    Configuration Groups", this feature simplifies configuring groups of roles
    that need to be configured differently, for example when running on nodes
    with heterogeneous hardware.
    *
    *
    - *Improved role to host assignment with Host Templates*. A host
    template defines a set of role configurations that can be applied to new
    hosts. This simplifies the process of adding hosts and instantiating the
    roles that should run on those hosts.

    - *AWS installation wizard* can bring up your entire from scratch
    (including EC2 instance creation), and optimize settings for the AWS
    environment. This is an excellent way to try out a fully functional CDH
    cluster managed by Cloudera Manager, although it is not intended for
    long-running production use.

    - *Support for Hive*, including the automatic creation of the Hive
    Metastore database. It also supports running the Hive Metastore Server and
    HiveServer2. If you have configured Hue or Impala, then upgrading to
    Cloudera Manager 4.5 will automatically create new Hive service(s), migrate
    the existing Hive related configuration over, and link Hue and Impala to
    the new Hive service(s).

    - *Resource management* enables sharing multiple workloads (such as
    MapReduce and Impala) on the same cluster, by partitioning cluster
    resources (CPU, memory) across different services.

    - *Removal of 50 node limit*. Cloudera Manager Free Edition no long
    limits the number of nodes it can manage.

    - *General usability and user interface improvements*.

    In addition, the Cloudera Manager 4.5 *Enterprise Edition* has added:

    - *Rolling restart* of services with zero/minimal downtime, used for
    effecting configuration changes, or upgrading your services (via parcels).
    You can do a rolling restart of an entire service, or just of certain
    roles. If you have enabled HDFS High Availability, you can also do a
    rolling restart on the entire cluster.

    - *Backup and Disaster Recovery* is an independently-licensed
    feature that replicates HDFS data files, and Hive Metastore and data files
    between clusters managed by different Cloudera Manager instances.

    - *HBase monitoring improvements* bring new health checks, metrics,
    domain specific events (such as compactions and splits), periodic region
    liveness checks (HBase canary) and data integrity checks (hbck).

    - *Advanced charting*. The host and service pages show a lot more
    charts on a lot more metrics, which provide useful tools for performance
    and diagnostics. In addition, you can build your own charts and dashboards
    with access to the raw metrics data using a new time-series query language,
    called tsquery.

    - *Proactive support* with automated cluster statistics collection.
    Periodic diagnostics gathering (enabled by default) allows Cloudera Support
    to discover any potential issues from the collected configuration files,
    log files, and other environmental information.

    - *SNMP alerts* enables easier integration with IT management tools.

    For more details on new features, please see the full release notes: [Free
    Edition<https://ccp.cloudera.com/display/FREE45DOC/New+Features+in+Cloudera+Manager+Free+Edition+4>]
    [Enterprise Edition<https://ccp.cloudera.com/display/ENT45DOC/New+Features+in+Cloudera+Manager+4>
    ]

    Getting Cloudera Manager 4.5:

    - Download at https://ccp.cloudera.com/**display/SUPPORT/Cloudera+**
    Manager+Downloads<https://ccp.cloudera.com/display/SUPPORT/Cloudera+Manager+Downloads>
    - Installation guide: https://ccp.cloudera.**com/display/FREE45DOC/**
    Cloudera+Manager+Free+Edition+**Installation+Guide<https://ccp.cloudera.com/display/FREE45DOC/Cloudera+Manager+Free+Edition+Installation+Guide>
    - Feedback and support: scm-...@cloudera.**org <
    https://groups.google.**com/a/cloudera.org/forum/?hl=**
    en&fromgroups#!forum/scm-users<https://groups.google.com/a/cloudera.org/forum/?hl=en&fromgroups#!forum/scm-users>
    **>

    We look forward to your feedback. Lastly, we'd like to thank everybody
    who tried out the 4.5 Beta. Your support makes Cloudera Manager a better
    product.

    Cheers,
    bc

    --
    Thanks,
    Darren
  • Darren Lo at Feb 28, 2013 at 7:24 pm
    Hi Philippe,

    Yes, this is normal. The upgrade wizard should have prompted you to add
    this role after performing your upgrade to CM4.5. You should have one Hive
    Metastore Server for each Hive service in CM4.5. The Hive Metastore Server
    is how CM implements the Hive concept of a Remote Metastore. Cloudera
    recommends using a remote metastore with Hive.

    Read more about the metastore modes here:
    https://ccp.cloudera.com/display/CDH4DOC/Hive+Installation#HiveInstallation-MetastoreDeploymentModes

    You can control whether CM configures all services to use the Hive
    Metastore Server or not via the Bypass Hive Metastore Server option in Hive
    Configuration (search for bypass in the search bar on the left of the Hive
    configuration page). After toggling this value, restart hive, hue, and
    impala, and deploy hive client configs (Click on hive service, look in
    actions menu on the right).

    To preserve old behavior, after upgrading to CM4.5, the Bypass Hive
    Metastore Server option will be checked by default. It's recommended to
    configure the Metastore Server and migrate to a remote metastore mode.

    Thanks,
    Darren

    On Thu, Feb 28, 2013 at 11:11 AM, Philippe Marseille wrote:

    We're using MySql for the metastore

    The Hive config was migrated successfully but for some reasons, the
    service will report an error if the "Metadata Server" role is not
    configured and running...

    Is this normal? I don't need this service...
    On Thursday, 28 February 2013 13:17:28 UTC-5, Darren Lo wrote:

    Hi Ben,

    You do not need to set any special configurations for the embedded
    postgres, though you may want to tune performance-related parameters in a
    production environment.

    The postgres driver is now automatically handled by CM for all hive
    configs managed by CM. That means hue, hive metastore server, impala, and
    hive configs updated the command Deploy Client Configs. Note that if you
    download client configs, then you'll need to make sure your machine has the
    driver and it is added properly to the classpath. Also note that oracle and
    mysql jars have special instructions, which are documented on the pages for
    setting up those databases.

    As you guessed, the beeswax safety valve information should be removed.

    Thanks,
    Darren

    On Thu, Feb 28, 2013 at 8:36 AM, Benjamin Kim wrote:

    bc,

    I have general question.

    Now that by default, the Hive metastore will be housed in the embedded
    PostgreSQL DB. Do we still need to set configurations based on the
    information contained at the link below or is it set for us?

    https://ccp.cloudera.com/**displ**ay/ENT4DOC/Installing+**and+**
    Configuring+an+External+**Postgr**eSQL+Database<https://ccp.cloudera.com/display/ENT4DOC/Installing+and+Configuring+an+External+PostgreSQL+Database>

    I assume that the PostgreSQL driver file is already provided so that
    copying it to /usr/lib/hive/lib is not necessary. In addition, the custom
    beeswax configurations shown below are no longer needed in the Hue
    Service Configuration Safety Valve.

    [beeswax]
    hive_home_dir=/usr/lib/hive
    hive_conf_dir=/etc/hive/conf

    Thanks,
    Ben
    On Tuesday, February 26, 2013 8:02:29 AM UTC-8, bc Wong wrote:

    On behalf of the Cloudera Manager team, I'm proud to announce the
    general availability of Cloudera Manager 4.5<https://ccp.cloudera.com/display/SUPPORT/Cloudera+Manager+Downloads>.
    This release packs tons of new features and improvements, including:

    - *Easy CDH upgrade* with a new packaging format called "parcel".
    Rather than manually upgrading the CDH packages across your cluster, you
    can now download, distribute and activate a new CDH version all from within
    Cloudera Manager.

    - *Improved configuration management for role instances*. You can
    now group an arbitrary set of roles instances (of the same type, e.g.
    DataNodes) together and manage their configuration as a unit. Called "Role
    Configuration Groups", this feature simplifies configuring groups of roles
    that need to be configured differently, for example when running on nodes
    with heterogeneous hardware.
    *
    *
    - *Improved role to host assignment with Host Templates*. A host
    template defines a set of role configurations that can be applied to new
    hosts. This simplifies the process of adding hosts and instantiating the
    roles that should run on those hosts.

    - *AWS installation wizard* can bring up your entire from scratch
    (including EC2 instance creation), and optimize settings for the AWS
    environment. This is an excellent way to try out a fully functional CDH
    cluster managed by Cloudera Manager, although it is not intended for
    long-running production use.

    - *Support for Hive*, including the automatic creation of the Hive
    Metastore database. It also supports running the Hive Metastore Server and
    HiveServer2. If you have configured Hue or Impala, then upgrading to
    Cloudera Manager 4.5 will automatically create new Hive service(s), migrate
    the existing Hive related configuration over, and link Hue and Impala to
    the new Hive service(s).

    - *Resource management* enables sharing multiple workloads (such as
    MapReduce and Impala) on the same cluster, by partitioning cluster
    resources (CPU, memory) across different services.

    - *Removal of 50 node limit*. Cloudera Manager Free Edition no long
    limits the number of nodes it can manage.

    - *General usability and user interface improvements*.

    In addition, the Cloudera Manager 4.5 *Enterprise Edition* has added:

    - *Rolling restart* of services with zero/minimal downtime, used
    for effecting configuration changes, or upgrading your services (via
    parcels). You can do a rolling restart of an entire service, or just of
    certain roles. If you have enabled HDFS High Availability, you can also do
    a rolling restart on the entire cluster.

    - *Backup and Disaster Recovery* is an independently-licensed
    feature that replicates HDFS data files, and Hive Metastore and data files
    between clusters managed by different Cloudera Manager instances.

    - *HBase monitoring improvements* bring new health checks, metrics,
    domain specific events (such as compactions and splits), periodic region
    liveness checks (HBase canary) and data integrity checks (hbck).

    - *Advanced charting*. The host and service pages show a lot more
    charts on a lot more metrics, which provide useful tools for performance
    and diagnostics. In addition, you can build your own charts and dashboards
    with access to the raw metrics data using a new time-series query language,
    called tsquery.

    - *Proactive support* with automated cluster statistics collection.
    Periodic diagnostics gathering (enabled by default) allows Cloudera Support
    to discover any potential issues from the collected configuration files,
    log files, and other environmental information.

    - *SNMP alerts* enables easier integration with IT management tools.

    For more details on new features, please see the full release notes: [Free
    Edition<https://ccp.cloudera.com/display/FREE45DOC/New+Features+in+Cloudera+Manager+Free+Edition+4>]
    [Enterprise Edition<https://ccp.cloudera.com/display/ENT45DOC/New+Features+in+Cloudera+Manager+4>
    ]

    Getting Cloudera Manager 4.5:

    - Download at https://ccp.cloudera.com/**di**splay/SUPPORT/Cloudera+
    **Manager**+Downloads<https://ccp.cloudera.com/display/SUPPORT/Cloudera+Manager+Downloads>
    - Installation guide: https://ccp.cloudera.**co**
    m/display/FREE45DOC/**Cloudera+**Manager+Free+Edition+**Installat**
    ion+Guide<https://ccp.cloudera.com/display/FREE45DOC/Cloudera+Manager+Free+Edition+Installation+Guide>
    - Feedback and support: scm-...@cloudera.**org **<
    https://groups.google.**com/a/**cloudera.org/forum/?hl=**en&**
    fromgroups#!forum/scm-users<https://groups.google.com/a/cloudera.org/forum/?hl=en&fromgroups#!forum/scm-users>
    **>

    We look forward to your feedback. Lastly, we'd like to thank everybody
    who tried out the 4.5 Beta. Your support makes Cloudera Manager a better
    product.

    Cheers,
    bc

    --
    Thanks,
    Darren

    --
    Thanks,
    Darren
  • Philippe Marseille at Feb 28, 2013 at 9:55 pm
    Alright.

    We'll migrate to the default metastore. We were using MySQL as a remote
    metastore.

    Everything looks fine now. I pushed the new parcels to all machines,
    removed all the RPMs and restarted the agent.

    Quick one : is there a way to re-install a parcel on a existing node? One
    of the machine had a bad config and ran out of disk space (oops!)
    On Thursday, 28 February 2013 14:24:41 UTC-5, Darren Lo wrote:

    Hi Philippe,

    Yes, this is normal. The upgrade wizard should have prompted you to add
    this role after performing your upgrade to CM4.5. You should have one Hive
    Metastore Server for each Hive service in CM4.5. The Hive Metastore Server
    is how CM implements the Hive concept of a Remote Metastore. Cloudera
    recommends using a remote metastore with Hive.

    Read more about the metastore modes here:

    https://ccp.cloudera.com/display/CDH4DOC/Hive+Installation#HiveInstallation-MetastoreDeploymentModes

    You can control whether CM configures all services to use the Hive
    Metastore Server or not via the Bypass Hive Metastore Server option in Hive
    Configuration (search for bypass in the search bar on the left of the Hive
    configuration page). After toggling this value, restart hive, hue, and
    impala, and deploy hive client configs (Click on hive service, look in
    actions menu on the right).

    To preserve old behavior, after upgrading to CM4.5, the Bypass Hive
    Metastore Server option will be checked by default. It's recommended to
    configure the Metastore Server and migrate to a remote metastore mode.

    Thanks,
    Darren


    On Thu, Feb 28, 2013 at 11:11 AM, Philippe Marseille <mars...@gmail.com<javascript:>
    wrote:
    We're using MySql for the metastore

    The Hive config was migrated successfully but for some reasons, the
    service will report an error if the "Metadata Server" role is not
    configured and running...

    Is this normal? I don't need this service...
    On Thursday, 28 February 2013 13:17:28 UTC-5, Darren Lo wrote:

    Hi Ben,

    You do not need to set any special configurations for the embedded
    postgres, though you may want to tune performance-related parameters in a
    production environment.

    The postgres driver is now automatically handled by CM for all hive
    configs managed by CM. That means hue, hive metastore server, impala, and
    hive configs updated the command Deploy Client Configs. Note that if you
    download client configs, then you'll need to make sure your machine has the
    driver and it is added properly to the classpath. Also note that oracle and
    mysql jars have special instructions, which are documented on the pages for
    setting up those databases.

    As you guessed, the beeswax safety valve information should be removed.

    Thanks,
    Darren

    On Thu, Feb 28, 2013 at 8:36 AM, Benjamin Kim wrote:

    bc,

    I have general question.

    Now that by default, the Hive metastore will be housed in the embedded
    PostgreSQL DB. Do we still need to set configurations based on the
    information contained at the link below or is it set for us?

    https://ccp.cloudera.com/**displ**ay/ENT4DOC/Installing+**and+**
    Configuring+an+External+**Postgr**eSQL+Database<https://ccp.cloudera.com/display/ENT4DOC/Installing+and+Configuring+an+External+PostgreSQL+Database>

    I assume that the PostgreSQL driver file is already provided so that
    copying it to /usr/lib/hive/lib is not necessary. In addition, the custom
    beeswax configurations shown below are no longer needed in the Hue
    Service Configuration Safety Valve.

    [beeswax]
    hive_home_dir=/usr/lib/hive
    hive_conf_dir=/etc/hive/conf

    Thanks,
    Ben
    On Tuesday, February 26, 2013 8:02:29 AM UTC-8, bc Wong wrote:

    On behalf of the Cloudera Manager team, I'm proud to announce the
    general availability of Cloudera Manager 4.5<https://ccp.cloudera.com/display/SUPPORT/Cloudera+Manager+Downloads>.
    This release packs tons of new features and improvements, including:

    - *Easy CDH upgrade* with a new packaging format called "parcel".
    Rather than manually upgrading the CDH packages across your cluster, you
    can now download, distribute and activate a new CDH version all from within
    Cloudera Manager.

    - *Improved configuration management for role instances*. You can
    now group an arbitrary set of roles instances (of the same type, e.g.
    DataNodes) together and manage their configuration as a unit. Called "Role
    Configuration Groups", this feature simplifies configuring groups of roles
    that need to be configured differently, for example when running on nodes
    with heterogeneous hardware.
    *
    *
    - *Improved role to host assignment with Host Templates*. A host
    template defines a set of role configurations that can be applied to new
    hosts. This simplifies the process of adding hosts and instantiating the
    roles that should run on those hosts.

    - *AWS installation wizard* can bring up your entire from scratch
    (including EC2 instance creation), and optimize settings for the AWS
    environment. This is an excellent way to try out a fully functional CDH
    cluster managed by Cloudera Manager, although it is not intended for
    long-running production use.

    - *Support for Hive*, including the automatic creation of the Hive
    Metastore database. It also supports running the Hive Metastore Server and
    HiveServer2. If you have configured Hue or Impala, then upgrading to
    Cloudera Manager 4.5 will automatically create new Hive service(s), migrate
    the existing Hive related configuration over, and link Hue and Impala to
    the new Hive service(s).

    - *Resource management* enables sharing multiple workloads (such
    as MapReduce and Impala) on the same cluster, by partitioning cluster
    resources (CPU, memory) across different services.

    - *Removal of 50 node limit*. Cloudera Manager Free Edition no
    long limits the number of nodes it can manage.

    - *General usability and user interface improvements*.

    In addition, the Cloudera Manager 4.5 *Enterprise Edition* has added:

    - *Rolling restart* of services with zero/minimal downtime, used
    for effecting configuration changes, or upgrading your services (via
    parcels). You can do a rolling restart of an entire service, or just of
    certain roles. If you have enabled HDFS High Availability, you can also do
    a rolling restart on the entire cluster.

    - *Backup and Disaster Recovery* is an independently-licensed
    feature that replicates HDFS data files, and Hive Metastore and data files
    between clusters managed by different Cloudera Manager instances.

    - *HBase monitoring improvements* bring new health checks,
    metrics, domain specific events (such as compactions and splits), periodic
    region liveness checks (HBase canary) and data integrity checks (hbck).

    - *Advanced charting*. The host and service pages show a lot more
    charts on a lot more metrics, which provide useful tools for performance
    and diagnostics. In addition, you can build your own charts and dashboards
    with access to the raw metrics data using a new time-series query language,
    called tsquery.

    - *Proactive support* with automated cluster statistics
    collection. Periodic diagnostics gathering (enabled by default) allows
    Cloudera Support to discover any potential issues from the collected
    configuration files, log files, and other environmental information.

    - *SNMP alerts* enables easier integration with IT management
    tools.

    For more details on new features, please see the full release notes: [Free
    Edition<https://ccp.cloudera.com/display/FREE45DOC/New+Features+in+Cloudera+Manager+Free+Edition+4>]
    [Enterprise Edition<https://ccp.cloudera.com/display/ENT45DOC/New+Features+in+Cloudera+Manager+4>
    ]

    Getting Cloudera Manager 4.5:

    - Download at https://ccp.cloudera.com/**di**
    splay/SUPPORT/Cloudera+**Manager**+Downloads<https://ccp.cloudera.com/display/SUPPORT/Cloudera+Manager+Downloads>
    - Installation guide: https://ccp.cloudera.**co**
    m/display/FREE45DOC/**Cloudera+**Manager+Free+Edition+**Installat**
    ion+Guide<https://ccp.cloudera.com/display/FREE45DOC/Cloudera+Manager+Free+Edition+Installation+Guide>
    - Feedback and support: scm-...@cloudera.**org **<
    https://groups.google.**com/a/**cloudera.org/forum/?hl=**en&**
    fromgroups#!forum/scm-users<https://groups.google.com/a/cloudera.org/forum/?hl=en&fromgroups#!forum/scm-users>
    **>

    We look forward to your feedback. Lastly, we'd like to thank everybody
    who tried out the 4.5 Beta. Your support makes Cloudera Manager a better
    product.

    Cheers,
    bc

    --
    Thanks,
    Darren

    --
    Thanks,
    Darren
  • Philip Langdale at Feb 28, 2013 at 11:07 pm
    Philippe,

    If the parcel deployment failed early enough, it will just be re-attempted.
    But otherwise, you can just rm -r the parcel
    directory (/opt/cloudera/parcels/<parcel name>) and CM will notice it's
    missing and re-deploy it.

    --phil

    On 28 February 2013 13:55, Philippe Marseille wrote:

    Alright.

    We'll migrate to the default metastore. We were using MySQL as a remote
    metastore.

    Everything looks fine now. I pushed the new parcels to all machines,
    removed all the RPMs and restarted the agent.

    Quick one : is there a way to re-install a parcel on a existing node? One
    of the machine had a bad config and ran out of disk space (oops!)

    On Thursday, 28 February 2013 14:24:41 UTC-5, Darren Lo wrote:

    Hi Philippe,

    Yes, this is normal. The upgrade wizard should have prompted you to add
    this role after performing your upgrade to CM4.5. You should have one Hive
    Metastore Server for each Hive service in CM4.5. The Hive Metastore Server
    is how CM implements the Hive concept of a Remote Metastore. Cloudera
    recommends using a remote metastore with Hive.

    Read more about the metastore modes here:
    https://ccp.cloudera.com/**display/CDH4DOC/Hive+**
    Installation#HiveInstallation-**MetastoreDeploymentModes<https://ccp.cloudera.com/display/CDH4DOC/Hive+Installation#HiveInstallation-MetastoreDeploymentModes>

    You can control whether CM configures all services to use the Hive
    Metastore Server or not via the Bypass Hive Metastore Server option in Hive
    Configuration (search for bypass in the search bar on the left of the Hive
    configuration page). After toggling this value, restart hive, hue, and
    impala, and deploy hive client configs (Click on hive service, look in
    actions menu on the right).

    To preserve old behavior, after upgrading to CM4.5, the Bypass Hive
    Metastore Server option will be checked by default. It's recommended to
    configure the Metastore Server and migrate to a remote metastore mode.

    Thanks,
    Darren

    On Thu, Feb 28, 2013 at 11:11 AM, Philippe Marseille wrote:

    We're using MySql for the metastore

    The Hive config was migrated successfully but for some reasons, the
    service will report an error if the "Metadata Server" role is not
    configured and running...

    Is this normal? I don't need this service...
    On Thursday, 28 February 2013 13:17:28 UTC-5, Darren Lo wrote:

    Hi Ben,

    You do not need to set any special configurations for the embedded
    postgres, though you may want to tune performance-related parameters in a
    production environment.

    The postgres driver is now automatically handled by CM for all hive
    configs managed by CM. That means hue, hive metastore server, impala, and
    hive configs updated the command Deploy Client Configs. Note that if you
    download client configs, then you'll need to make sure your machine has the
    driver and it is added properly to the classpath. Also note that oracle and
    mysql jars have special instructions, which are documented on the pages for
    setting up those databases.

    As you guessed, the beeswax safety valve information should be removed.

    Thanks,
    Darren

    On Thu, Feb 28, 2013 at 8:36 AM, Benjamin Kim wrote:

    bc,

    I have general question.

    Now that by default, the Hive metastore will be housed in the embedded
    PostgreSQL DB. Do we still need to set configurations based on the
    information contained at the link below or is it set for us?

    https://ccp.cloudera.com/**displ****ay/ENT4DOC/Installing+**and+**Conf
    **iguring+an+External+**Postgr**eSQL**+Database<https://ccp.cloudera.com/display/ENT4DOC/Installing+and+Configuring+an+External+PostgreSQL+Database>

    I assume that the PostgreSQL driver file is already provided so that
    copying it to /usr/lib/hive/lib is not necessary. In addition, the custom
    beeswax configurations shown below are no longer needed in the Hue
    Service Configuration Safety Valve.

    [beeswax]
    hive_home_dir=/usr/lib/hive
    hive_conf_dir=/etc/hive/conf

    Thanks,
    Ben
    On Tuesday, February 26, 2013 8:02:29 AM UTC-8, bc Wong wrote:

    On behalf of the Cloudera Manager team, I'm proud to announce the
    general availability of Cloudera Manager 4.5<https://ccp.cloudera.com/display/SUPPORT/Cloudera+Manager+Downloads>.
    This release packs tons of new features and improvements, including:

    - *Easy CDH upgrade* with a new packaging format called "parcel".
    Rather than manually upgrading the CDH packages across your cluster, you
    can now download, distribute and activate a new CDH version all from within
    Cloudera Manager.

    - *Improved configuration management for role instances*. You can
    now group an arbitrary set of roles instances (of the same type, e.g.
    DataNodes) together and manage their configuration as a unit. Called "Role
    Configuration Groups", this feature simplifies configuring groups of roles
    that need to be configured differently, for example when running on nodes
    with heterogeneous hardware.
    *
    *
    - *Improved role to host assignment with Host Templates*. A host
    template defines a set of role configurations that can be applied to new
    hosts. This simplifies the process of adding hosts and instantiating the
    roles that should run on those hosts.

    - *AWS installation wizard* can bring up your entire from scratch
    (including EC2 instance creation), and optimize settings for the AWS
    environment. This is an excellent way to try out a fully functional CDH
    cluster managed by Cloudera Manager, although it is not intended for
    long-running production use.

    - *Support for Hive*, including the automatic creation of the
    Hive Metastore database. It also supports running the Hive Metastore Server
    and HiveServer2. If you have configured Hue or Impala, then upgrading to
    Cloudera Manager 4.5 will automatically create new Hive service(s), migrate
    the existing Hive related configuration over, and link Hue and Impala to
    the new Hive service(s).

    - *Resource management* enables sharing multiple workloads (such
    as MapReduce and Impala) on the same cluster, by partitioning cluster
    resources (CPU, memory) across different services.

    - *Removal of 50 node limit*. Cloudera Manager Free Edition no
    long limits the number of nodes it can manage.

    - *General usability and user interface improvements*.

    In addition, the Cloudera Manager 4.5 *Enterprise Edition* has added:

    - *Rolling restart* of services with zero/minimal downtime, used
    for effecting configuration changes, or upgrading your services (via
    parcels). You can do a rolling restart of an entire service, or just of
    certain roles. If you have enabled HDFS High Availability, you can also do
    a rolling restart on the entire cluster.

    - *Backup and Disaster Recovery* is an independently-licensed
    feature that replicates HDFS data files, and Hive Metastore and data files
    between clusters managed by different Cloudera Manager instances.

    - *HBase monitoring improvements* bring new health checks,
    metrics, domain specific events (such as compactions and splits), periodic
    region liveness checks (HBase canary) and data integrity checks (hbck).

    - *Advanced charting*. The host and service pages show a lot more
    charts on a lot more metrics, which provide useful tools for performance
    and diagnostics. In addition, you can build your own charts and dashboards
    with access to the raw metrics data using a new time-series query language,
    called tsquery.

    - *Proactive support* with automated cluster statistics
    collection. Periodic diagnostics gathering (enabled by default) allows
    Cloudera Support to discover any potential issues from the collected
    configuration files, log files, and other environmental information.

    - *SNMP alerts* enables easier integration with IT management
    tools.

    For more details on new features, please see the full release notes: [Free
    Edition<https://ccp.cloudera.com/display/FREE45DOC/New+Features+in+Cloudera+Manager+Free+Edition+4>]
    [Enterprise Edition<https://ccp.cloudera.com/display/ENT45DOC/New+Features+in+Cloudera+Manager+4>
    ]

    Getting Cloudera Manager 4.5:

    - Download at https://ccp.cloudera.com/**di****
    splay/SUPPORT/Cloudera+**Manager****+Downloads<https://ccp.cloudera.com/display/SUPPORT/Cloudera+Manager+Downloads>
    - Installation guide: https://ccp.cloudera.**co****
    m/display/FREE45DOC/**Cloudera+**M**anager+Free+Edition+**
    Installat**i**on+Guide<https://ccp.cloudera.com/display/FREE45DOC/Cloudera+Manager+Free+Edition+Installation+Guide>
    - Feedback and support: scm-...@cloudera.**org ****<
    https://groups.google.**com/a/**c**loudera.org/forum/?hl=**en&**
    fromg**roups#!forum/scm-users<https://groups.google.com/a/cloudera.org/forum/?hl=en&fromgroups#!forum/scm-users>
    **>

    We look forward to your feedback. Lastly, we'd like to thank
    everybody who tried out the 4.5 Beta. Your support makes Cloudera Manager a
    better product.

    Cheers,
    bc

    --
    Thanks,
    Darren

    --
    Thanks,
    Darren
  • Philippe Marseille at Mar 1, 2013 at 1:39 pm
    I just realized I read something wrong.

    The MetaStore service in cloudera manager is not a database, it's Hive's
    "Remote Metastore"... The "proxy" or "relay" service to my Metastore
    Database. I'll keep my MySql instance... but I'll just enable the
    MetaStore server in the config and change the config on the clients.

    That way, I won't have to propagate the MySql login and drivers to the
    clients !

    https://cwiki.apache.org/Hive/adminmanual-metastoreadmin.html

    "In remote metastore setup, all Hive Clients will make a connection a
    metastore server which in turn queries the datastore (MySQL in this
    example) for metadata. Metastore server and client communicate using Thrift<http://incubator.apache.org/thrift>
    Protocol. Starting with Hive 0.5.0, you can start a thrift server by
    executing the following command:"
    On Thursday, 28 February 2013 16:55:35 UTC-5, Philippe Marseille wrote:

    Alright.

    We'll migrate to the default metastore. We were using MySQL as a remote
    metastore.

    Everything looks fine now. I pushed the new parcels to all machines,
    removed all the RPMs and restarted the agent.

    Quick one : is there a way to re-install a parcel on a existing node? One
    of the machine had a bad config and ran out of disk space (oops!)
    On Thursday, 28 February 2013 14:24:41 UTC-5, Darren Lo wrote:

    Hi Philippe,

    Yes, this is normal. The upgrade wizard should have prompted you to add
    this role after performing your upgrade to CM4.5. You should have one Hive
    Metastore Server for each Hive service in CM4.5. The Hive Metastore Server
    is how CM implements the Hive concept of a Remote Metastore. Cloudera
    recommends using a remote metastore with Hive.

    Read more about the metastore modes here:

    https://ccp.cloudera.com/display/CDH4DOC/Hive+Installation#HiveInstallation-MetastoreDeploymentModes

    You can control whether CM configures all services to use the Hive
    Metastore Server or not via the Bypass Hive Metastore Server option in Hive
    Configuration (search for bypass in the search bar on the left of the Hive
    configuration page). After toggling this value, restart hive, hue, and
    impala, and deploy hive client configs (Click on hive service, look in
    actions menu on the right).

    To preserve old behavior, after upgrading to CM4.5, the Bypass Hive
    Metastore Server option will be checked by default. It's recommended to
    configure the Metastore Server and migrate to a remote metastore mode.

    Thanks,
    Darren

    On Thu, Feb 28, 2013 at 11:11 AM, Philippe Marseille wrote:

    We're using MySql for the metastore

    The Hive config was migrated successfully but for some reasons, the
    service will report an error if the "Metadata Server" role is not
    configured and running...

    Is this normal? I don't need this service...
    On Thursday, 28 February 2013 13:17:28 UTC-5, Darren Lo wrote:

    Hi Ben,

    You do not need to set any special configurations for the embedded
    postgres, though you may want to tune performance-related parameters in a
    production environment.

    The postgres driver is now automatically handled by CM for all hive
    configs managed by CM. That means hue, hive metastore server, impala, and
    hive configs updated the command Deploy Client Configs. Note that if you
    download client configs, then you'll need to make sure your machine has the
    driver and it is added properly to the classpath. Also note that oracle and
    mysql jars have special instructions, which are documented on the pages for
    setting up those databases.

    As you guessed, the beeswax safety valve information should be removed.

    Thanks,
    Darren

    On Thu, Feb 28, 2013 at 8:36 AM, Benjamin Kim wrote:

    bc,

    I have general question.

    Now that by default, the Hive metastore will be housed in the embedded
    PostgreSQL DB. Do we still need to set configurations based on the
    information contained at the link below or is it set for us?

    https://ccp.cloudera.com/**displ**ay/ENT4DOC/Installing+**and+**
    Configuring+an+External+**Postgr**eSQL+Database<https://ccp.cloudera.com/display/ENT4DOC/Installing+and+Configuring+an+External+PostgreSQL+Database>

    I assume that the PostgreSQL driver file is already provided so that
    copying it to /usr/lib/hive/lib is not necessary. In addition, the custom
    beeswax configurations shown below are no longer needed in the Hue
    Service Configuration Safety Valve.

    [beeswax]
    hive_home_dir=/usr/lib/hive
    hive_conf_dir=/etc/hive/conf

    Thanks,
    Ben
    On Tuesday, February 26, 2013 8:02:29 AM UTC-8, bc Wong wrote:

    On behalf of the Cloudera Manager team, I'm proud to announce the
    general availability of Cloudera Manager 4.5<https://ccp.cloudera.com/display/SUPPORT/Cloudera+Manager+Downloads>.
    This release packs tons of new features and improvements, including:

    - *Easy CDH upgrade* with a new packaging format called "parcel".
    Rather than manually upgrading the CDH packages across your cluster, you
    can now download, distribute and activate a new CDH version all from within
    Cloudera Manager.

    - *Improved configuration management for role instances*. You can
    now group an arbitrary set of roles instances (of the same type, e.g.
    DataNodes) together and manage their configuration as a unit. Called "Role
    Configuration Groups", this feature simplifies configuring groups of roles
    that need to be configured differently, for example when running on nodes
    with heterogeneous hardware.
    *
    *
    - *Improved role to host assignment with Host Templates*. A host
    template defines a set of role configurations that can be applied to new
    hosts. This simplifies the process of adding hosts and instantiating the
    roles that should run on those hosts.

    - *AWS installation wizard* can bring up your entire from scratch
    (including EC2 instance creation), and optimize settings for the AWS
    environment. This is an excellent way to try out a fully functional CDH
    cluster managed by Cloudera Manager, although it is not intended for
    long-running production use.

    - *Support for Hive*, including the automatic creation of the
    Hive Metastore database. It also supports running the Hive Metastore Server
    and HiveServer2. If you have configured Hue or Impala, then upgrading to
    Cloudera Manager 4.5 will automatically create new Hive service(s), migrate
    the existing Hive related configuration over, and link Hue and Impala to
    the new Hive service(s).

    - *Resource management* enables sharing multiple workloads (such
    as MapReduce and Impala) on the same cluster, by partitioning cluster
    resources (CPU, memory) across different services.

    - *Removal of 50 node limit*. Cloudera Manager Free Edition no
    long limits the number of nodes it can manage.

    - *General usability and user interface improvements*.

    In addition, the Cloudera Manager 4.5 *Enterprise Edition* has added:

    - *Rolling restart* of services with zero/minimal downtime, used
    for effecting configuration changes, or upgrading your services (via
    parcels). You can do a rolling restart of an entire service, or just of
    certain roles. If you have enabled HDFS High Availability, you can also do
    a rolling restart on the entire cluster.

    - *Backup and Disaster Recovery* is an independently-licensed
    feature that replicates HDFS data files, and Hive Metastore and data files
    between clusters managed by different Cloudera Manager instances.

    - *HBase monitoring improvements* bring new health checks,
    metrics, domain specific events (such as compactions and splits), periodic
    region liveness checks (HBase canary) and data integrity checks (hbck).

    - *Advanced charting*. The host and service pages show a lot more
    charts on a lot more metrics, which provide useful tools for performance
    and diagnostics. In addition, you can build your own charts and dashboards
    with access to the raw metrics data using a new time-series query language,
    called tsquery.

    - *Proactive support* with automated cluster statistics
    collection. Periodic diagnostics gathering (enabled by default) allows
    Cloudera Support to discover any potential issues from the collected
    configuration files, log files, and other environmental information.

    - *SNMP alerts* enables easier integration with IT management
    tools.

    For more details on new features, please see the full release notes: [Free
    Edition<https://ccp.cloudera.com/display/FREE45DOC/New+Features+in+Cloudera+Manager+Free+Edition+4>]
    [Enterprise Edition<https://ccp.cloudera.com/display/ENT45DOC/New+Features+in+Cloudera+Manager+4>
    ]

    Getting Cloudera Manager 4.5:

    - Download at https://ccp.cloudera.com/**di**
    splay/SUPPORT/Cloudera+**Manager**+Downloads<https://ccp.cloudera.com/display/SUPPORT/Cloudera+Manager+Downloads>
    - Installation guide: https://ccp.cloudera.**co**
    m/display/FREE45DOC/**Cloudera+**Manager+Free+Edition+**Installat*
    *ion+Guide<https://ccp.cloudera.com/display/FREE45DOC/Cloudera+Manager+Free+Edition+Installation+Guide>
    - Feedback and support: scm-...@cloudera.**org **<
    https://groups.google.**com/a/**cloudera.org/forum/?hl=**en&**
    fromgroups#!forum/scm-users<https://groups.google.com/a/cloudera.org/forum/?hl=en&fromgroups#!forum/scm-users>
    **>

    We look forward to your feedback. Lastly, we'd like to thank
    everybody who tried out the 4.5 Beta. Your support makes Cloudera Manager a
    better product.

    Cheers,
    bc

    --
    Thanks,
    Darren

    --
    Thanks,
    Darren
  • Darren Lo at Mar 1, 2013 at 6:51 pm
    Yes, that's correct. Sorry for the earlier confusion.

    Hive Metastore Server manages Hive's Remote Metastore process. It still
    needs to be configured with a database.

    This page is helpful for those trying to understand what "Remote Metastore"
    means:
    https://ccp.cloudera.com/display/CDH4DOC/Hive+Installation#HiveInstallation-MetastoreDeploymentModes

    Other than avoiding mass distribution of your mysql passwords and drivers,
    using the Hive Metastore Server also allows you to easily control access to
    the database, making it easy to perform tasks such as backup and upgrade,
    which require that there are no other active connections to the Database.

    Thanks,
    Darren

    On Fri, Mar 1, 2013 at 5:39 AM, Philippe Marseille wrote:

    I just realized I read something wrong.

    The MetaStore service in cloudera manager is not a database, it's Hive's
    "Remote Metastore"... The "proxy" or "relay" service to my Metastore
    Database. I'll keep my MySql instance... but I'll just enable the
    MetaStore server in the config and change the config on the clients.

    That way, I won't have to propagate the MySql login and drivers to the
    clients !

    https://cwiki.apache.org/Hive/adminmanual-metastoreadmin.html

    "In remote metastore setup, all Hive Clients will make a connection a
    metastore server which in turn queries the datastore (MySQL in this
    example) for metadata. Metastore server and client communicate using
    Thrift <http://incubator.apache.org/thrift> Protocol. Starting with Hive
    0.5.0, you can start a thrift server by executing the following command:"

    On Thursday, 28 February 2013 16:55:35 UTC-5, Philippe Marseille wrote:

    Alright.

    We'll migrate to the default metastore. We were using MySQL as a remote
    metastore.

    Everything looks fine now. I pushed the new parcels to all machines,
    removed all the RPMs and restarted the agent.

    Quick one : is there a way to re-install a parcel on a existing node?
    One of the machine had a bad config and ran out of disk space (oops!)
    On Thursday, 28 February 2013 14:24:41 UTC-5, Darren Lo wrote:

    Hi Philippe,

    Yes, this is normal. The upgrade wizard should have prompted you to add
    this role after performing your upgrade to CM4.5. You should have one Hive
    Metastore Server for each Hive service in CM4.5. The Hive Metastore Server
    is how CM implements the Hive concept of a Remote Metastore. Cloudera
    recommends using a remote metastore with Hive.

    Read more about the metastore modes here:
    https://ccp.cloudera.com/**display/CDH4DOC/Hive+**
    Installation#HiveInstallation-**MetastoreDeploymentModes<https://ccp.cloudera.com/display/CDH4DOC/Hive+Installation#HiveInstallation-MetastoreDeploymentModes>

    You can control whether CM configures all services to use the Hive
    Metastore Server or not via the Bypass Hive Metastore Server option in Hive
    Configuration (search for bypass in the search bar on the left of the Hive
    configuration page). After toggling this value, restart hive, hue, and
    impala, and deploy hive client configs (Click on hive service, look in
    actions menu on the right).

    To preserve old behavior, after upgrading to CM4.5, the Bypass Hive
    Metastore Server option will be checked by default. It's recommended to
    configure the Metastore Server and migrate to a remote metastore mode.

    Thanks,
    Darren

    On Thu, Feb 28, 2013 at 11:11 AM, Philippe Marseille wrote:

    We're using MySql for the metastore

    The Hive config was migrated successfully but for some reasons, the
    service will report an error if the "Metadata Server" role is not
    configured and running...

    Is this normal? I don't need this service...
    On Thursday, 28 February 2013 13:17:28 UTC-5, Darren Lo wrote:

    Hi Ben,

    You do not need to set any special configurations for the embedded
    postgres, though you may want to tune performance-related parameters in a
    production environment.

    The postgres driver is now automatically handled by CM for all hive
    configs managed by CM. That means hue, hive metastore server, impala, and
    hive configs updated the command Deploy Client Configs. Note that if you
    download client configs, then you'll need to make sure your machine has the
    driver and it is added properly to the classpath. Also note that oracle and
    mysql jars have special instructions, which are documented on the pages for
    setting up those databases.

    As you guessed, the beeswax safety valve information should be removed.

    Thanks,
    Darren

    On Thu, Feb 28, 2013 at 8:36 AM, Benjamin Kim wrote:

    bc,

    I have general question.

    Now that by default, the Hive metastore will be housed in the
    embedded PostgreSQL DB. Do we still need to set configurations based on the
    information contained at the link below or is it set for us?

    https://ccp.cloudera.com/**displ****ay/ENT4DOC/Installing+**and+**
    Conf**iguring+an+External+**Postgr**eSQL**+Database<https://ccp.cloudera.com/display/ENT4DOC/Installing+and+Configuring+an+External+PostgreSQL+Database>

    I assume that the PostgreSQL driver file is already provided so that
    copying it to /usr/lib/hive/lib is not necessary. In addition, the custom
    beeswax configurations shown below are no longer needed in the Hue
    Service Configuration Safety Valve.

    [beeswax]
    hive_home_dir=/usr/lib/hive
    hive_conf_dir=/etc/hive/conf

    Thanks,
    Ben
    On Tuesday, February 26, 2013 8:02:29 AM UTC-8, bc Wong wrote:

    On behalf of the Cloudera Manager team, I'm proud to announce the
    general availability of Cloudera Manager 4.5<https://ccp.cloudera.com/display/SUPPORT/Cloudera+Manager+Downloads>.
    This release packs tons of new features and improvements, including:

    - *Easy CDH upgrade* with a new packaging format called
    "parcel". Rather than manually upgrading the CDH packages across your
    cluster, you can now download, distribute and activate a new CDH version
    all from within Cloudera Manager.

    - *Improved configuration management for role instances*. You
    can now group an arbitrary set of roles instances (of the same type, e.g.
    DataNodes) together and manage their configuration as a unit. Called "Role
    Configuration Groups", this feature simplifies configuring groups of roles
    that need to be configured differently, for example when running on nodes
    with heterogeneous hardware.
    *
    *
    - *Improved role to host assignment with Host Templates*. A host
    template defines a set of role configurations that can be applied to new
    hosts. This simplifies the process of adding hosts and instantiating the
    roles that should run on those hosts.

    - *AWS installation wizard* can bring up your entire from
    scratch (including EC2 instance creation), and optimize settings for the
    AWS environment. This is an excellent way to try out a fully functional CDH
    cluster managed by Cloudera Manager, although it is not intended for
    long-running production use.

    - *Support for Hive*, including the automatic creation of the
    Hive Metastore database. It also supports running the Hive Metastore Server
    and HiveServer2. If you have configured Hue or Impala, then upgrading to
    Cloudera Manager 4.5 will automatically create new Hive service(s), migrate
    the existing Hive related configuration over, and link Hue and Impala to
    the new Hive service(s).

    - *Resource management* enables sharing multiple workloads (such
    as MapReduce and Impala) on the same cluster, by partitioning cluster
    resources (CPU, memory) across different services.

    - *Removal of 50 node limit*. Cloudera Manager Free Edition no
    long limits the number of nodes it can manage.

    - *General usability and user interface improvements*.

    In addition, the Cloudera Manager 4.5 *Enterprise Edition* has
    added:

    - *Rolling restart* of services with zero/minimal downtime, used
    for effecting configuration changes, or upgrading your services (via
    parcels). You can do a rolling restart of an entire service, or just of
    certain roles. If you have enabled HDFS High Availability, you can also do
    a rolling restart on the entire cluster.

    - *Backup and Disaster Recovery* is an independently-licensed
    feature that replicates HDFS data files, and Hive Metastore and data files
    between clusters managed by different Cloudera Manager instances.

    - *HBase monitoring improvements* bring new health checks,
    metrics, domain specific events (such as compactions and splits), periodic
    region liveness checks (HBase canary) and data integrity checks (hbck).

    - *Advanced charting*. The host and service pages show a lot
    more charts on a lot more metrics, which provide useful tools for
    performance and diagnostics. In addition, you can build your own charts and
    dashboards with access to the raw metrics data using a new time-series
    query language, called tsquery.

    - *Proactive support* with automated cluster statistics
    collection. Periodic diagnostics gathering (enabled by default) allows
    Cloudera Support to discover any potential issues from the collected
    configuration files, log files, and other environmental information.

    - *SNMP alerts* enables easier integration with IT management
    tools.

    For more details on new features, please see the full release
    notes: [Free Edition<https://ccp.cloudera.com/display/FREE45DOC/New+Features+in+Cloudera+Manager+Free+Edition+4>]
    [Enterprise Edition<https://ccp.cloudera.com/display/ENT45DOC/New+Features+in+Cloudera+Manager+4>
    ]

    Getting Cloudera Manager 4.5:

    - Download at https://ccp.cloudera.com/**di****
    splay/SUPPORT/Cloudera+**Manager****+Downloads<https://ccp.cloudera.com/display/SUPPORT/Cloudera+Manager+Downloads>
    - Installation guide: https://ccp.cloudera.**co****
    m/display/FREE45DOC/**Cloudera+**M**anager+Free+Edition+**
    Installat**i**on+Guide<https://ccp.cloudera.com/display/FREE45DOC/Cloudera+Manager+Free+Edition+Installation+Guide>
    - Feedback and support: scm-...@cloudera.**org ****<
    https://groups.google.**com/a/**c**loudera.org/forum/?hl=**en&**
    fromg**roups#!forum/scm-users<https://groups.google.com/a/cloudera.org/forum/?hl=en&fromgroups#!forum/scm-users>
    **>

    We look forward to your feedback. Lastly, we'd like to thank
    everybody who tried out the 4.5 Beta. Your support makes Cloudera Manager a
    better product.

    Cheers,
    bc

    --
    Thanks,
    Darren

    --
    Thanks,
    Darren

    --
    Thanks,
    Darren

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedFeb 28, '13 at 6:17p
activeMar 1, '13 at 6:51p
posts7
users3
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase