Author: buildbot
Date: Sat Nov 22 19:20:25 2014
New Revision: 930127
Log:
Staging update by buildbot for slider
Modified:
websites/staging/slider/trunk/content/ (props changed)
websites/staging/slider/trunk/content/release_notes/release-0.50.2.html
Propchange: websites/staging/slider/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Nov 22 19:20:25 2014
@@ -1 +1 @@
-1641110
+1641111
Modified:
websites/staging/slider/trunk/content/release_notes/release-0.50.2.html
==============================================================================
--- websites/staging/slider/trunk/content/release_notes/release-0.50.2.html
(original)
+++ websites/staging/slider/trunk/content/release_notes/release-0.50.2.html Sat
Nov 22 19:20:25 2014
@@ -177,45 +177,15 @@ Latest release: <strong>0.40-incubating<
limitations under the License.
-->
-<h1 id="apache-slider-release-0502-incubating">Apache Slider Release 0.50.2
(incubating)</h1>
+<h1 id="apache-slider-release-0600-incubating">Apache Slider Release 0.60.0
(incubating)</h1>
<p>August 2014</p>
-<p>This release is built against Apache Hadoop 2.4.1, HBase 0.98.4 and
Accumulo 1.6.0</p>
+<p>This release is built against Apache Hadoop 2.6.0, HBase 0.98.4 and
Accumulo 1.6.1</p>
<h2 id="key-changes">Key changes</h2>
-<ol>
-<li>
-<p>Slider now has an integral Chaos Monkey <a
href="https://issues.apache.org/jira/browse/SLIDER-202">SLIDER-202</a>.
-This can be configured to start through options in <code>internal.json</code>;
it will kill
-a random container or the AM itself based on configured properties. This is
intended
-for use in testing âthough may be used in production if desired, and if the
-application and YARN cluster configured to tolerate the failures.</p>
-</li>
-<li>
-<p>Slider runs on Java 6 <a
href="https://issues.apache.org/jira/browse/SLIDER-322">SLIDER-322</a>.
-We plan to keep it Java 6-compatible until Hadoop core upgrades to Java 7.</p>
-</li>
-<li>
-<p>Improved Port allocation and management in component instances.
-(<a href="https://issues.apache.org/jira/browse/SLIDER-219">SLIDER-219</a>,
- <a href="https://issues.apache.org/jira/browse/SLIDER-273">SLIDER-273</a></p>
-</li>
-</ol>
+<p>TBD</p>
<h2 id="incompatible-changes">Incompatible Changes</h2>
-<h3 id="slider-77-use-a-window-for-tracking-container-failures"><a
href="https://issues.apache.org/jira/browse/SLIDER-77">SLIDER-77</a>: use a
window for tracking container failures.</h3>
-<p>Previously a simple threshold,
<code>"internal.container.failure.threshold"</code> set the
-limit for the number of container failures tolerated for the life of an
application.</p>
-<p>This has now been reworked to support</p>
-<h1 id="a-time-bounded-window-for-failures">a time-bounded window for
failures</h1>
-<h1 id="placement-in-resourcesjson-as-yarncontainerfailurethreshold">placement
in <code>resources.json</code> as
<code>"yarn.container.failure.threshold"</code></h1>
-<h1 id="resetchanging-during-cluster-flex">reset/changing during cluster
flex</h1>
-<h1 id="configurable-in-a-combination-of-days-hours-and-minutes">Configurable
in a combination of days, hours and minutes.</h1>
-<p>This is a major change âand is necessary to support long-lived
applications with
-a slow failure rate, while still detecting and reacting to the situation where
-many containers are failing in a short period of time.</p>
-<p>Because the property name has changed, any cluster where this had been
changed from
-the default (which is still five) will not pick up the changes. Please use the
-new name and set the value in the global section of
<code>resources.json</code></p>
+<p>TBD</p>
<h2 id="other-changes">Other changes</h2>
-<p>The full list of completed issues is <a
href="https://issues.apache.org/jira/browse/SLIDER/fixforversion/12326949/">visible
in the Apache JIRA</a></p>
+<p>The full list of completed issues is <a
href="https://issues.apache.org/jira/browse/SLIDER/fixforversion/12327198/">visible
in the Apache JIRA</a></p>
</div>
<div id="footer">