See https://hudson.apache.org/hudson/job/Hadoop-Common-trunk/568/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 1852 lines...]
... 12 more
Caused by: hud
reloginFromKeytab() should happen even if TGT can't be found
Key: HADOOP-7091
URL: https://issues.apache.org/jira/browse/HADOOP-7091
Project: Hadoop Common
Issue Type: Bug
Thanks guys,
I really appreciate your help.
Niels Basjes
2011/1/6 Doug Cutting :
> The problem was that the submitter could transition from "Patch Available"
> to "In Progress", following the "Resume Progress" transition, but the
> submitter cannot then transtion anywhere from "In Progress", onl
The problem was that the submitter could transition from "Patch
Available" to "In Progress", following the "Resume Progress" transition,
but the submitter cannot then transtion anywhere from "In Progress",
only the assignee could. I fixed that, so that the assignee can no
longer follow that tr
Niels-
For new patches, just cancel the current and submit will become
available again. Also, there's no need to delete prior versions of
the patch; it's better to keep them around for posterity and
comparison. Hudson will run against whatever is uploaded most
recently (this is important for b
[
https://issues.apache.org/jira/browse/HADOOP-6855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Steffl resolved HADOOP-6855.
-
Resolution: Won't Fix
Fix Version/s: (was: 0.22.0)
0.20.4
This pat
I seem to have selected the wrong option in Jira to get the latest
patch handled.
For some reason the option to indicate a new patch has been made
available is no longer present.
https://issues.apache.org/jira/browse/HADOOP-7076
What did I do wrong and what can I do to fix this?
Thanks.
--
Met
On 01/05/2011 12:44 AM, Christopher Smith wrote:
Yes, my C program can reach 100MB/s or even 110MB/s when writing data to
the
disk sequentially, but with direct I/O enabled, the maximal throughput is
about
140MB/s. But the biggest difference is CPU usage.
Without direct I/O, operating system uses
