You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by "Eric Newton (JIRA)" <ji...@apache.org> on 2012/07/02 18:59:21 UTC
[jira] [Updated] (ACCUMULO-613) release Accumulo 1.3.6
[ https://issues.apache.org/jira/browse/ACCUMULO-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Newton updated ACCUMULO-613:
---------------------------------
Description:
A number of improvements make it time to release the next version on the 1.3 branch. Some highlights include:
* Fixing a problem where the master gets stuck loading a table with a large root tablet (ACCUMULO-542)
* Fixing a problem where the master fails to balance tablets after a tablet server fails (ACCUMULO-202)
* Fix of potential data loss that can occur if a failure coincides with a recovery (ACCUMULO-444)
* Improved locality for MapReduce with AccumuloInputFormat (ACCUMULO-395)
* Fixed garbage collector problems when tracer is offline (ACCUMULO-499)
* Scripted building the 0.3 version of libthrift (ACCUMULO-563)
* Connections from master to tserver now properly reset after failure (ACCUMULO-530)
* Many more to be found in this [list of tickets|https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=fixVersion+%3D+%221.3.6%22+AND+project+%3D+ACCUMULO].
Before the release, perform the following tests for quality assurance:
# -Run the functional test suite.-
# -Run the continuous ingest test over at least a 12 hour period, and verify results.-
# Update CHANGES
was:
A number of improvements make it time to release the next version on the 1.3 branch. Some highlights include:
* Fixing a problem where the master gets stuck loading a table with a large root tablet (ACCUMULO-542)
* Fixing a problem where the master fails to balance tablets after a tablet server fails (ACCUMULO-202)
* Fix of potential data loss that can occur if a failure coincides with a recovery (ACCUMULO-444)
* Improved locality for MapReduce with AccumuloInputFormat (ACCUMULO-395)
* Fixed garbage collector problems when tracer is offline (ACCUMULO-499)
* Scripted building the 0.3 version of libthrift (ACCUMULO-563)
* Connections from master to tserver now properly reset after failure (ACCUMULO-530)
* Many more to be found in this [list of tickets|https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=fixVersion+%3D+%221.3.6%22+AND+project+%3D+ACCUMULO].
Before the release, perform the following tests for quality assurance:
# -Run the functional test suite.-
# Run the continuous ingest test over at least a 12 hour period, and verify results.
# Run the random-walk tests over at least a 12 hour period.
> release Accumulo 1.3.6
> ----------------------
>
> Key: ACCUMULO-613
> URL: https://issues.apache.org/jira/browse/ACCUMULO-613
> Project: Accumulo
> Issue Type: Task
> Affects Versions: 1.3.6
> Reporter: Adam Fuchs
> Assignee: Eric Newton
> Priority: Blocker
> Fix For: 1.3.6
>
>
> A number of improvements make it time to release the next version on the 1.3 branch. Some highlights include:
> * Fixing a problem where the master gets stuck loading a table with a large root tablet (ACCUMULO-542)
> * Fixing a problem where the master fails to balance tablets after a tablet server fails (ACCUMULO-202)
> * Fix of potential data loss that can occur if a failure coincides with a recovery (ACCUMULO-444)
> * Improved locality for MapReduce with AccumuloInputFormat (ACCUMULO-395)
> * Fixed garbage collector problems when tracer is offline (ACCUMULO-499)
> * Scripted building the 0.3 version of libthrift (ACCUMULO-563)
> * Connections from master to tserver now properly reset after failure (ACCUMULO-530)
> * Many more to be found in this [list of tickets|https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=fixVersion+%3D+%221.3.6%22+AND+project+%3D+ACCUMULO].
> Before the release, perform the following tests for quality assurance:
> # -Run the functional test suite.-
> # -Run the continuous ingest test over at least a 12 hour period, and verify results.-
> # Update CHANGES
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira