JvmMetrics can't distinguish between jvms with same processName
---
Key: HADOOP-6874
URL: https://issues.apache.org/jira/browse/HADOOP-6874
Project: Hadoop Common
Issue Type: Bug
using delegation token over hftp for long running clients (part of hdfs 1296)
-
Key: HADOOP-6873
URL: https://issues.apache.org/jira/browse/HADOOP-6873
Project: Hadoop Common
ChecksumFs#listStatus should filter out .crc files
--
Key: HADOOP-6872
URL: https://issues.apache.org/jira/browse/HADOOP-6872
Project: Hadoop Common
Issue Type: Bug
Components: fs
When the value of a configuration key is set to its unresolved form, it causes
the IllegalStateException in Configuration.get() stating that substitution
depth is too large.
---
Add FileSystem#listLocatedStatus to list a directory's content together with
each file's block locations
Key: HADOOP-6870
URL: https://issues.apache.org/jira/
[
https://issues.apache.org/jira/browse/HADOOP-6810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik resolved HADOOP-6810.
Resolution: Later
I'd like to close it for now as 'Later' until Common has enough
[Herriot] Implement a functionality for creating either file or folder in task
attempt folder while job is running.
Key: HADOOP-6869
URL: https:/
I seem to be ok with the little bit of _20 I've been using.
On Jul 21, 2010, at 5:58 AM, Bill Au wrote:
> Now that jdk 1.6.0_21 is out, has anyone been running it with Hadoop? We
> have also had problem running Hadoop with 1.6.0_18. So what version of
> 1.6.0 would people recommend for use wit
Now that jdk 1.6.0_21 is out, has anyone been running it with Hadoop? We
have also had problem running Hadoop with 1.6.0_18. So what version of
1.6.0 would people recommend for use with Hadoop?
Bill
On Tue, Apr 6, 2010 at 12:09 PM, Steve Loughran wrote:
> Todd Lipcon wrote:
>
>> I was seeing