Hortonworks » Mahadev Konarhttp://hortonworks.com
Develops, Distributes and Supports Enterprise Apache Hadoop.Tue, 31 Mar 2015 21:53:36 +0000en-UShourly1http://wordpress.org/?v=4.1.1Apache Ambari 1.5.1 is Released!http://hortonworks.com/blog/apache-ambari-1-5-1-released/
http://hortonworks.com/blog/apache-ambari-1-5-1-released/#commentsTue, 22 Apr 2014 20:12:18 +0000http://hortonworks.com/?p=52164Yesterday the Apache Ambari community proudly released version 1.5.1. This is the result of constant, concerted collaboration among the Ambari project’s many members. This release represents the work of over 30 individuals over 5 months and, combined with the Ambari 1.5.0 release, resolves more than 1,000 JIRAs.

This version of Ambari makes huge strides in simplifying the deployment, management and monitoring of large Hadoop clusters, including those running Hortonworks Data Platform 2.1.

Ambari 1.5.1 contains many new features – let’s take a look at those.

Maintenance Mode

This feature silences alerts on Services and Hosts, an ideal feature for when you need to perform cluster maintenance. The Hadoop operator can put Services or Hosts “out of service” and alerts will be suspended for those items.

Rolling Restarts

Rolling restarts minimize cluster downtime and service impact when making configuration changes across many hosts.…

]]>Yesterday the Apache Ambari community proudly released version 1.5.1. This is the result of constant, concerted collaboration among the Ambari project’s many members. This release represents the work of over 30 individuals over 5 months and, combined with the Ambari 1.5.0 release, resolves more than 1,000 JIRAs.

This version of Ambari makes huge strides in simplifying the deployment, management and monitoring of large Hadoop clusters, including those running Hortonworks Data Platform 2.1.

Ambari 1.5.1 contains many new features – let’s take a look at those.

Maintenance Mode

This feature silences alerts on Services and Hosts, an ideal feature for when you need to perform cluster maintenance. The Hadoop operator can put Services or Hosts “out of service” and alerts will be suspended for those items.

Rolling Restarts

Rolling restarts minimize cluster downtime and service impact when making configuration changes across many hosts. Administrators can initiate a rolling restart of cluster components (such as DataNodes), with the option of including only hosts with configuration changes.

Bulk Host Operations

As clusters grow larger, Hadoop operators need to host operations on batches of hosts. This feature makes those “bulk” operations easy and available via the Ambari Web interface. Supported bulk operations are: Stop, Start, Restart, Decommission and Maintenance Mode. These operations may be applied to all hosts, the filtered group of hosts or a selected group of hosts.

Decommission of Task Trackers, Node Managers and Region Servers

It is sometimes necessary to remove data from existing services for storage elsewhere while performing maintenance. Decommission allows the Hadoop operator to phase out service components without bringing down services or losing data.

Add Service Control

This allows Hadoop operators to install clusters with the minimum amount of required services, and then add on additional services later with the new “Add Service” control in the Ambari Web UI. This permits more agile, flexible growth of components and services in a cluster.

MANY THANKS to all the contributors that made the Ambari 1.5.1 release possible!

Special Bonus: Ambari Blueprints

This release also includes a technical preview of the Ambari Blueprints feature. With Ambari Blueprints, you can simplify the automation of cluster installs by defining the stack to use, the components layout and the configuration. With just a few API calls, you have a cluster up and running. This is particularly helpful for virtual and cloud environments where the Hadoop operator wants to create ad hoc discovery clusters or dev and test clusters, in an automated and consistent fashion.

Learn More

]]>http://hortonworks.com/blog/apache-zookeeper-3-4-5-released/feed/0ZooKeeper 3.4.4 is Now Availablehttp://hortonworks.com/blog/zookeeper-3-4-4-is-now-available/
http://hortonworks.com/blog/zookeeper-3-4-4-is-now-available/#commentsMon, 24 Sep 2012 15:44:48 +0000http://hortonworks.com/?p=10324Apache ZooKeeper release 3.4.4 is now available. This is a bug fix release including 50 bug fixes. Following is a summary of the critical issues fixed in the release.

As you might have noticed we have been marking all the previous 3.4.* releases as Alpha and beta. After having a couple of releases out (3.4.0, 3.4.1, 3.4.2, 3.4.3), we in the ZooKeeper community have decided to upgrade 3.4.4 as a stable release.

Acknowledgements

Thanks to everyone who contributed towards the release including our users who reported the bugs in 3.4.4.…

As you might have noticed we have been marking all the previous 3.4.* releases as Alpha and beta. After having a couple of releases out (3.4.0, 3.4.1, 3.4.2, 3.4.3), we in the ZooKeeper community have decided to upgrade 3.4.4 as a stable release.

Acknowledgements

Thanks to everyone who contributed towards the release including our users who reported the bugs in 3.4.4.

]]>http://hortonworks.com/blog/zookeeper-3-4-4-is-now-available/feed/1Apache ZooKeeper 3.4.3 Releasedhttp://hortonworks.com/blog/apache-zookeeper-3-4-3-released/
http://hortonworks.com/blog/apache-zookeeper-3-4-3-released/#commentsTue, 14 Feb 2012 14:44:45 +0000http://hortonworks.com/?p=2857For those of you new to Apache ZooKeeper, it is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. To learn more about ZooKeeper, please visit the Apache ZooKeeper homepage.

As part of stabilizing Apache ZooKeeper 3.4 branch, ZooKeeper 3.4.3 has just been released. It is a bug fix release on the 3.4 branch and fixes 17 issues out of which 1 is very critical and can cause data inconsistency (ZOOKEEPER-1367). This particular issue can lead to data inconsistencies in your ZooKeeper servers. If you are currently using any of the 3.4.* releases, please make sure you upgrade to 3.4.3.

The release also includes a fix to make SASL login context names configurable (ZOOKEEPER-1373). This allows ZooKeeper to integrate well with all the Apache Hadoop releases. The release also fixes some documentation and logging issues.…

]]>For those of you new to Apache ZooKeeper, it is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. To learn more about ZooKeeper, please visit the Apache ZooKeeper homepage.

As part of stabilizing Apache ZooKeeper 3.4 branch, ZooKeeper 3.4.3 has just been released. It is a bug fix release on the 3.4 branch and fixes 17 issues out of which 1 is very critical and can cause data inconsistency (ZOOKEEPER-1367). This particular issue can lead to data inconsistencies in your ZooKeeper servers. If you are currently using any of the 3.4.* releases, please make sure you upgrade to 3.4.3.

The release also includes a fix to make SASL login context names configurable (ZOOKEEPER-1373). This allows ZooKeeper to integrate well with all the Apache Hadoop releases. The release also fixes some documentation and logging issues.

Note that the release notes include changes to ZooKeeper dependencies adding slf4j-api and slf4j-log4j12 as new dependencies, which was introduced in 3.4 release branch as part of ZOOKEEPER-850.

Stability of 3.4.3

As you might have noticed we have been marking all the previous 3.4.* releases as Alpha. After releasing several 3.4 versions (3.4.0, 3.4.1, 3.4.2), the ZooKeeper community has decided to upgrade 3.4.3 to a beta release.

Improved testing in ZooKeeper

As we move on to new features on trunk for a 3.5 release, we have been discussing ways to improve release testing. This was one of the important discussion points brought up during our MeetUp. As a part of the 3.5 release, the ZooKeeper community intends to focus more on testing and reliability. We look forward to more engagement from the user community to help test ZooKeeper releases and build better testing frameworks.

Acknowledgements

Thanks to everyone who contributed towards the release including our users who reported the bugs in 3.4.2.