[
https://issues.apache.org/jira/browse/ACCUMULO-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581369#comment-13581369
]
Eric Newton edited comment on ACCUMULO-1053 at 2/19/13 3:33 PM:
----------------------------------------------------------------
Keith writes on the dev list:
bq. Seems like this loop should be moved to isReady() part of repo. This has
two advantages. It does not tie up a Fate thread. Also if lots of leases need
to be recovered it can cycle through all of them calling recoverLease once,
instead of waiting for each one to be done. Maybe this would spin up a lot of
parallel work in the namenode
I agree: I'll refactor the code.
was (Author: ecn):
Keith writes on the dev list:
bq. Seems like this loop should be moved to isRead() part of repo. This has
two advantages. It does not tie up a Fate thread. Also if lots of leases need
to be recovered it can cycle through all of them calling recoverLease once,
instead of waiting for each one to be done. Maybe this would spin up a lot of
parallel work in the namenode
I agree: I'll refactor the code.
> continuous ingest detected data loss
> ------------------------------------
>
> Key: ACCUMULO-1053
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1053
> Project: Accumulo
> Issue Type: Bug
> Components: test, tserver
> Reporter: Eric Newton
> Assignee: Eric Newton
> Priority: Critical
> Fix For: 1.5.0
>
>
> Now that we're logging directly HDFS, we added datanodes to the agitator.
> That is, we are now killing data nodes during ingest, and now we are losing
> data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
