FAQ
Dear Cloudera Manager users,

I am pleased to announce the availability of Cloudera Manager 4.0.3. This
is an enhancement release, with several improvements to configurability and
usability. Some key enhancements include:

Configurable user/group settings for Oozie, HBase, YARN, MapReduce, and
HDFS processes
Support new configuration parameters for MapReduce services.
Auto configuration of reserved space for non-DFS use parameter for HDFS
service.
Improved cluster upgrade process
Support for LDAP users/groups that belong to more than one Organization
Unit (OU).
Flexibility with distribution of key tabs when using existing Kerberos
infrastructure (e.g. Active Directory).
Support for trash interval setting for client configurations

You can read the detailed release notes at
https://ccp.cloudera.com/display/ENT4DOC/New+Features+in+Cloudera+Manager+4.0

Here are the steps for upgrading to the latest version of Cloudera Manager:
https://ccp.cloudera.com/display/FREE4DOC/Upgrade+from+Cloudera+Manager+4+to+the+Latest+Version+of+Cloudera+Manager+4

Thank you for using Cloudera Manager!

-Aditya

Search Discussions

  • Ansonism at Jul 25, 2012 at 6:56 pm
    Hi, I have a question. I downloaded the latest bin file
    (cloudera-manager-installer.bin) on Debian linux I am running.

    When I execute to install it's looking for
    when in fact cloudera-manager-daemons-4.0.3-1.cm403.p0.50.x86_64.rpm<http://archive.cloudera.com/cm4/redhat/6/x86_64/cm/4/RPMS/x86_64/cloudera-manager-daemons-4.0.3-1.cm403.p0.50.x86_64.rpm> exists.
      Is there a config to force the install to use 4.0.3?
    On Thursday, July 19, 2012 5:59:10 PM UTC-4, Aditya Acharya wrote:

    Dear Cloudera Manager users,

    I am pleased to announce the availability of Cloudera Manager 4.0.3. This
    is an enhancement release, with several improvements to configurability and
    usability. Some key enhancements include:

    Configurable user/group settings for Oozie, HBase, YARN, MapReduce, and
    HDFS processes
    Support new configuration parameters for MapReduce services.
    Auto configuration of reserved space for non-DFS use parameter for HDFS
    service.
    Improved cluster upgrade process
    Support for LDAP users/groups that belong to more than one Organization
    Unit (OU).
    Flexibility with distribution of key tabs when using existing Kerberos
    infrastructure (e.g. Active Directory).
    Support for trash interval setting for client configurations

    You can read the detailed release notes at
    https://ccp.cloudera.com/display/ENT4DOC/New+Features+in+Cloudera+Manager+4.0

    Here are the steps for upgrading to the latest version of Cloudera
    Manager:
    https://ccp.cloudera.com/display/FREE4DOC/Upgrade+from+Cloudera+Manager+4+to+the+Latest+Version+of+Cloudera+Manager+4

    Thank you for using Cloudera Manager!

    -Aditya
  • Aditya Acharya at Jul 25, 2012 at 6:47 pm
    What is the installer looking for? I think you forgot to put that in your
    email.

    cloudera-manager-daemons-4.0.3-1.cm403.p0.50.x86_64.rpm<http://archive.cloudera.com/cm4/redhat/6/x86_64/cm/4/RPMS/x86_64/cloudera-manager-daemons-4.0.3-1.cm403.p0.50.x86_64.rpm>
    is
    a 4.0.3 package.
    On Wed, Jul 25, 2012 at 10:55 AM, ansonism wrote:

    Hi, I have a question. I downloaded the latest bin file
    (cloudera-manager-installer.bin) on Debian linux I am running.

    When I execute to install it's looking for
    when in fact cloudera-manager-daemons-4.0.3-1.cm403.p0.50.x86_64.rpm<http://archive.cloudera.com/cm4/redhat/6/x86_64/cm/4/RPMS/x86_64/cloudera-manager-daemons-4.0.3-1.cm403.p0.50.x86_64.rpm> exists.
    Is there a config to force the install to use 4.0.3?

    On Thursday, July 19, 2012 5:59:10 PM UTC-4, Aditya Acharya wrote:

    Dear Cloudera Manager users,

    I am pleased to announce the availability of Cloudera Manager 4.0.3. This
    is an enhancement release, with several improvements to configurability and
    usability. Some key enhancements include:

    Configurable user/group settings for Oozie, HBase, YARN, MapReduce, and
    HDFS processes
    Support new configuration parameters for MapReduce services.
    Auto configuration of reserved space for non-DFS use parameter for HDFS
    service.
    Improved cluster upgrade process
    Support for LDAP users/groups that belong to more than one Organization
    Unit (OU).
    Flexibility with distribution of key tabs when using existing Kerberos
    infrastructure (e.g. Active Directory).
    Support for trash interval setting for client configurations

    You can read the detailed release notes at https://ccp.cloudera.com/**
    display/ENT4DOC/New+Features+**in+Cloudera+Manager+4.0<https://ccp.cloudera.com/display/ENT4DOC/New+Features+in+Cloudera+Manager+4.0>

    Here are the steps for upgrading to the latest version of Cloudera
    Manager: https://ccp.cloudera.**com/display/FREE4DOC/Upgrade+**
    from+Cloudera+Manager+4+to+**the+Latest+Version+of+**Cloudera+Manager+4<https://ccp.cloudera.com/display/FREE4DOC/Upgrade+from+Cloudera+Manager+4+to+the+Latest+Version+of+Cloudera+Manager+4>

    Thank you for using Cloudera Manager!

    -Aditya
  • Ansonism at Jul 25, 2012 at 8:11 pm
    This is what's in the log:

    Setting up Install Process
    Resolving Dependencies
    --> Running transaction check
    ---> Package cloudera-manager-server.x86_64 0:4.0.1-1.cm401.p0.44 will be
    installed
    --> Processing Dependency: cloudera-manager-daemons = 4.0.1 for package:
    cloudera-manager-server-4.0.1-1.cm401.p0.44.x86_64
    --> Running transaction check
    ---> Package cloudera-manager-daemons.x86_64 0:4.0.1-1.cm401.p0.44 will be
    installed
    --> Finished Dependency Resolution

    Dependencies Resolved

    ================================================================================
      Package Arch Version Repository
    Size
    ================================================================================
    Installing:
      cloudera-manager-server x86_64 4.0.1-1.cm401.p0.44 cloudera-manager
      5.7 k
    Installing for dependencies:
      cloudera-manager-daemons x86_64 4.0.1-1.cm401.p0.44 cloudera-manager
    96 M

    Transaction Summary
    ================================================================================
    Install 2 Package(s)

    Installed size: 115 M
    Downloading Packages:
    Setting up and reading Presto delta metadata
    Processing delta metadata
    Package(s) data still to download: 96 M
    http://archive.cloudera.com/cm4/redhat/6/x86_64/cm/4/RPMS/x86_64/cloudera-manager-daemons-4.0.1-1.cm401.p0.44.x86_64.rpm:
    [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404"
    Trying other mirror.
    http://archive.cloudera.com/cm4/redhat/6/x86_64/cm/4/RPMS/x86_64/cloudera-manager-server-4.0.1-1.cm401.p0.44.x86_64.rpm:
    [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404"
    Trying other mirror.


    looks like it's going for the older version for some reason.
    On Wednesday, July 25, 2012 2:42:16 PM UTC-4, Aditya Acharya wrote:

    What is the installer looking for? I think you forgot to put that in your
    email.

    cloudera-manager-daemons-4.0.3-1.cm403.p0.50.x86_64.rpm<http://archive.cloudera.com/cm4/redhat/6/x86_64/cm/4/RPMS/x86_64/cloudera-manager-daemons-4.0.3-1.cm403.p0.50.x86_64.rpm> is
    a 4.0.3 package.
    On Wed, Jul 25, 2012 at 10:55 AM, ansonism wrote:

    Hi, I have a question. I downloaded the latest bin file
    (cloudera-manager-installer.bin) on Debian linux I am running.

    When I execute to install it's looking for
    when in fact cloudera-manager-daemons-4.0.3-1.cm403.p0.50.x86_64.rpm<http://archive.cloudera.com/cm4/redhat/6/x86_64/cm/4/RPMS/x86_64/cloudera-manager-daemons-4.0.3-1.cm403.p0.50.x86_64.rpm> exists.
    Is there a config to force the install to use 4.0.3?

    On Thursday, July 19, 2012 5:59:10 PM UTC-4, Aditya Acharya wrote:

    Dear Cloudera Manager users,

    I am pleased to announce the availability of Cloudera Manager 4.0.3.
    This is an enhancement release, with several improvements to
    configurability and usability. Some key enhancements include:

    Configurable user/group settings for Oozie, HBase, YARN, MapReduce, and
    HDFS processes
    Support new configuration parameters for MapReduce services.
    Auto configuration of reserved space for non-DFS use parameter for HDFS
    service.
    Improved cluster upgrade process
    Support for LDAP users/groups that belong to more than one Organization
    Unit (OU).
    Flexibility with distribution of key tabs when using existing Kerberos
    infrastructure (e.g. Active Directory).
    Support for trash interval setting for client configurations

    You can read the detailed release notes at https://ccp.cloudera.com/**
    display/ENT4DOC/New+Features+**in+Cloudera+Manager+4.0<https://ccp.cloudera.com/display/ENT4DOC/New+Features+in+Cloudera+Manager+4.0>

    Here are the steps for upgrading to the latest version of Cloudera
    Manager: https://ccp.cloudera.**com/display/FREE4DOC/Upgrade+**
    from+Cloudera+Manager+4+to+**the+Latest+Version+of+**Cloudera+Manager+4<https://ccp.cloudera.com/display/FREE4DOC/Upgrade+from+Cloudera+Manager+4+to+the+Latest+Version+of+Cloudera+Manager+4>

    Thank you for using Cloudera Manager!

    -Aditya
  • Ansonism at Jul 25, 2012 at 8:55 pm
    never mind resolved issue...turned out to be the yum cache directory had
    some old params in there for some reason
    On Wednesday, July 25, 2012 3:09:05 PM UTC-4, ansonism wrote:

    This is what's in the log:

    Setting up Install Process
    Resolving Dependencies
    --> Running transaction check
    ---> Package cloudera-manager-server.x86_64 0:4.0.1-1.cm401.p0.44 will be
    installed
    --> Processing Dependency: cloudera-manager-daemons = 4.0.1 for package:
    cloudera-manager-server-4.0.1-1.cm401.p0.44.x86_64
    --> Running transaction check
    ---> Package cloudera-manager-daemons.x86_64 0:4.0.1-1.cm401.p0.44 will be
    installed
    --> Finished Dependency Resolution

    Dependencies Resolved


    ================================================================================
    Package Arch Version Repository
    Size

    ================================================================================
    Installing:
    cloudera-manager-server x86_64 4.0.1-1.cm401.p0.44 cloudera-manager
    5.7 k
    Installing for dependencies:
    cloudera-manager-daemons x86_64 4.0.1-1.cm401.p0.44 cloudera-manager
    96 M

    Transaction Summary

    ================================================================================
    Install 2 Package(s)

    Installed size: 115 M
    Downloading Packages:
    Setting up and reading Presto delta metadata
    Processing delta metadata
    Package(s) data still to download: 96 M

    http://archive.cloudera.com/cm4/redhat/6/x86_64/cm/4/RPMS/x86_64/cloudera-manager-daemons-4.0.1-1.cm401.p0.44.x86_64.rpm:
    [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404"
    Trying other mirror.

    http://archive.cloudera.com/cm4/redhat/6/x86_64/cm/4/RPMS/x86_64/cloudera-manager-server-4.0.1-1.cm401.p0.44.x86_64.rpm:
    [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404"
    Trying other mirror.


    looks like it's going for the older version for some reason.
    On Wednesday, July 25, 2012 2:42:16 PM UTC-4, Aditya Acharya wrote:

    What is the installer looking for? I think you forgot to put that in your
    email.

    cloudera-manager-daemons-4.0.3-1.cm403.p0.50.x86_64.rpm<http://archive.cloudera.com/cm4/redhat/6/x86_64/cm/4/RPMS/x86_64/cloudera-manager-daemons-4.0.3-1.cm403.p0.50.x86_64.rpm> is
    a 4.0.3 package.
    On Wed, Jul 25, 2012 at 10:55 AM, ansonism wrote:

    Hi, I have a question. I downloaded the latest bin file
    (cloudera-manager-installer.bin) on Debian linux I am running.

    When I execute to install it's looking for
    when in fact cloudera-manager-daemons-4.0.3-1.cm403.p0.50.x86_64.rpm<http://archive.cloudera.com/cm4/redhat/6/x86_64/cm/4/RPMS/x86_64/cloudera-manager-daemons-4.0.3-1.cm403.p0.50.x86_64.rpm> exists.
    Is there a config to force the install to use 4.0.3?

    On Thursday, July 19, 2012 5:59:10 PM UTC-4, Aditya Acharya wrote:

    Dear Cloudera Manager users,

    I am pleased to announce the availability of Cloudera Manager 4.0.3.
    This is an enhancement release, with several improvements to
    configurability and usability. Some key enhancements include:

    Configurable user/group settings for Oozie, HBase, YARN, MapReduce, and
    HDFS processes
    Support new configuration parameters for MapReduce services.
    Auto configuration of reserved space for non-DFS use parameter for HDFS
    service.
    Improved cluster upgrade process
    Support for LDAP users/groups that belong to more than one Organization
    Unit (OU).
    Flexibility with distribution of key tabs when using existing Kerberos
    infrastructure (e.g. Active Directory).
    Support for trash interval setting for client configurations

    You can read the detailed release notes at https://ccp.cloudera.com/**
    display/ENT4DOC/New+Features+**in+Cloudera+Manager+4.0<https://ccp.cloudera.com/display/ENT4DOC/New+Features+in+Cloudera+Manager+4.0>

    Here are the steps for upgrading to the latest version of Cloudera
    Manager: https://ccp.cloudera.**com/display/FREE4DOC/Upgrade+**
    from+Cloudera+Manager+4+to+**the+Latest+Version+of+**Cloudera+Manager+4<https://ccp.cloudera.com/display/FREE4DOC/Upgrade+from+Cloudera+Manager+4+to+the+Latest+Version+of+Cloudera+Manager+4>

    Thank you for using Cloudera Manager!

    -Aditya
  • Megha Agrawal at Aug 8, 2012 at 2:49 pm
    Hi,

    I am having issues in installing the Cloudera Manager 4.0.3.

    Whenever I try to install it, it gives the following error:
    Failed to configure Embedded Service and Configuration Database. See
    /var/log/cloudera-manager-
    installer/6.init-embedded-db.log for details.

    When I look into log file I get following:
    psql: FATAL: no pg_hba.conf entry for host "192.168.30.1", user
    "cloudera-scm", database "postgres", SSL off


    Now, to resolve this I have done following changes:
    in postgresql.conf --------- did this : listen_addresses = '*'
    in pg_hba.conf -------------- added:

    host postgres cloudera-scm 192.168.30.1/24 trust
    host all all 192.168.5.30/24 trust
    host all all 192.168.30.30/24 trust
    host postgres all 192.168.30.1/32 trust


    But then also I get the above error.

    Note: I uninstalled the previous cloudera manager completely and now when I
    try to install it again, it shows the above error.

    Thanks,
    Megha

    On Thursday, July 19, 2012 5:59:10 PM UTC-4, Aditya Acharya wrote:

    Dear Cloudera Manager users,

    I am pleased to announce the availability of Cloudera Manager 4.0.3. This
    is an enhancement release, with several improvements to configurability and
    usability. Some key enhancements include:

    Configurable user/group settings for Oozie, HBase, YARN, MapReduce, and
    HDFS processes
    Support new configuration parameters for MapReduce services.
    Auto configuration of reserved space for non-DFS use parameter for HDFS
    service.
    Improved cluster upgrade process
    Support for LDAP users/groups that belong to more than one Organization
    Unit (OU).
    Flexibility with distribution of key tabs when using existing Kerberos
    infrastructure (e.g. Active Directory).
    Support for trash interval setting for client configurations

    You can read the detailed release notes at
    https://ccp.cloudera.com/display/ENT4DOC/New+Features+in+Cloudera+Manager+4.0

    Here are the steps for upgrading to the latest version of Cloudera
    Manager:
    https://ccp.cloudera.com/display/FREE4DOC/Upgrade+from+Cloudera+Manager+4+to+the+Latest+Version+of+Cloudera+Manager+4

    Thank you for using Cloudera Manager!

    -Aditya

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedJul 19, '12 at 9:59p
activeAug 8, '12 at 2:49p
posts6
users3
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase