[
https://issues.apache.org/jira/browse/ACCUMULO-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206169#comment-13206169
]
Keith Turner commented on ACCUMULO-145:
---------------------------------------
Completed a round of continuous ingest on a 10 node cluster w/o agitation.
Verification succeeded, no data was lost. With the new running scans feature
on the monitor page I noticed one node was slow during verification. It had
queued scans when no other node did. Finally all mappers were waiting on it.
Not sure why it was slow yet, does not appear to be an Accumulo bug because
pings are taking hundreds of milliseconds. This probably slowed ingest too,
but the slowest node will slow all other nodes during ingest unlike
verification so its not as easily detectable on the monitor page. During
ingest clients write to all nodes, during verification clients mappers read
individual tablets. For this run of about 14.5 hours 18.2 billion nodes were
ingested and nothing was lost. Wonder if it would have gone faster w/o the
slow node. Next I will run w/ agitation
> Release Accumulo 1.4
> --------------------
>
> Key: ACCUMULO-145
> URL: https://issues.apache.org/jira/browse/ACCUMULO-145
> Project: Accumulo
> Issue Type: Task
> Reporter: John Vines
> Assignee: Eric Newton
> Priority: Blocker
> Labels: release
> Fix For: 1.4.0
>
>
> The 1.4 branch of Accumulo is preparing release. This ticket should take us
> through the release process. On the list of things left to do are:
> 1. Test as per http://incubator.apache.org/accumulo/governance/releasing.html
> 2. Document the release, including the documentation that needs to done
> according to Accumulo-68
> 3. Purge GPL content as per Accumulo-92
> 3. Tag the code
> 4. Do the build
> 5. Sign the build
> 6. Take a vote
> See also http://incubator.apache.org/guides/releasemanagement.html ,
> http://incubator.apache.org/accumulo/governance/releasing.html
--
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
