[
https://issues.apache.org/jira/browse/HADOOP-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484749
]
Philippe Gassmann commented on HADOOP-1130:
---
The closeAll() method should also remove ClientFinalizer from
NPE in TaskTracker RenitTrackerAction
--
Key: HADOOP-1171
URL: https://issues.apache.org/jira/browse/HADOOP-1171
Project: Hadoop
Issue Type: Bug
Components: mapred
Reporter: Koji Nog
[
https://issues.apache.org/jira/browse/HADOOP-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484721
]
Devaraj Das commented on HADOOP-1159:
-
Sorry, should have looked at this patch earlier. The problem with this pa
[
https://issues.apache.org/jira/browse/HADOOP-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484713
]
Devaraj Das commented on HADOOP-1001:
-
+1
> the output of the map is not type checked against the specified typ
[
https://issues.apache.org/jira/browse/HADOOP-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484712
]
Devaraj Das commented on HADOOP-1167:
-
+1
> InMemoryFileSystem uses synchronizedtMaps with maps that are locked
[
https://issues.apache.org/jira/browse/HADOOP-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484711
]
Hadoop QA commented on HADOOP-1170:
---
+1, because http://issues.apache.org/jira/secure/attachment/12354393/1170.pat
[
https://issues.apache.org/jira/browse/HADOOP-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Bolotin updated HADOOP-1170:
-
Status: Patch Available (was: Open)
> Very high CPU usage on data nodes because of FSDataset.ch
[
https://issues.apache.org/jira/browse/HADOOP-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Bolotin updated HADOOP-1170:
-
Attachment: 1170.patch
Attached patch removes checkDataDir() calls from DataXceiveServer.run() m
Very high CPU usage on data nodes because of FSDataset.checkDataDir() on every
connect
--
Key: HADOOP-1170
URL: https://issues.apache.org/jira/browse/HADOOP-1170
Proj
if a series of patches like this one are committed, is it OK to do
them all under one Jira issue?
As long as they all make it in a single release, this is fine with
me. In theory we can even map issues to multiple releases, each in
which they're partially fixed, but that could get confusin
We should file a Jira on it.
I agree CheckDir() is called too many times and too expensive. I don't
think it serves anything important or essential purpose. I vote for
removing it. Anyone ever seen this check fail and/or the failure being
useful for cluster functionality?
Raghu.
Igor Boloti
While investigating performance issues in our Hadoop DFS/MapReduce
cluster I saw very high CPU usage by DataNode processes.
Stack trace showed following on most of the data nodes:
"[EMAIL PROTECTED]" daemon prio=1
tid=0x2aaacb5b7bd0 nid=0x5940 runnable
[0x4166a000..0x4166ac
[
https://issues.apache.org/jira/browse/HADOOP-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484668
]
Hadoop QA commented on HADOOP-1169:
---
+1, because
http://issues.apache.org/jira/secure/attachment/12354378/hadoop1
[
https://issues.apache.org/jira/browse/HADOOP-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484665
]
James P. White commented on HADOOP-1161:
>> I do not like the idea of applying the same patch more than one
[
https://issues.apache.org/jira/browse/HADOOP-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
[EMAIL PROTECTED] updated HADOOP-1169:
--
Status: Patch Available (was: Open)
Patch attached.
> CopyFiles skips src files of s
[
https://issues.apache.org/jira/browse/HADOOP-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
[EMAIL PROTECTED] updated HADOOP-1169:
--
Attachment: hadoop1169.patch
> CopyFiles skips src files of s3 urls
>
>
> Oh, i misunderstood your question. I am switching buffer serialization to
> just plain bytes except for 5 characters that are escaped (essentially
> similar to string serialization as if the string were iso-8859-1.)
>
I'm not sure I follow. I think string serialization implies UTF-8
enco
CopyFiles skips src files of s3 urls
Key: HADOOP-1169
URL: https://issues.apache.org/jira/browse/HADOOP-1169
Project: Hadoop
Issue Type: Bug
Components: util
Affects Versions: 0.12.2
Not able to refresh file cache
--
Key: HADOOP-1168
URL: https://issues.apache.org/jira/browse/HADOOP-1168
Project: Hadoop
Issue Type: Bug
Components: mapred
Affects Versions: 0.12.2
Repor
[
https://issues.apache.org/jira/browse/HADOOP-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484647
]
Owen O'Malley commented on HADOOP-1161:
---
> I do not like the idea of applying the same patch more than one pla
[
https://issues.apache.org/jira/browse/HADOOP-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484638
]
Hadoop QA commented on HADOOP-1167:
---
+1, because
http://issues.apache.org/jira/secure/attachment/12354373/h1167.p
[
https://issues.apache.org/jira/browse/HADOOP-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484633
]
Hadoop QA commented on HADOOP-1123:
---
+1, because
http://issues.apache.org/jira/secure/attachment/12354361/1123_wi
[
https://issues.apache.org/jira/browse/HADOOP-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484629
]
Raghu Angadi commented on HADOOP-1161:
--
> We already do have a branch for each major release. The question is
[
https://issues.apache.org/jira/browse/HADOOP-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated HADOOP-1167:
--
Attachment: h1167.patch
> InMemoryFileSystem uses synchronizedtMaps with maps that are locked
[
https://issues.apache.org/jira/browse/HADOOP-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated HADOOP-1167:
--
Status: Patch Available (was: Open)
> InMemoryFileSystem uses synchronizedtMaps with maps tha
InMemoryFileSystem uses synchronizedtMaps with maps that are locked anyways
---
Key: HADOOP-1167
URL: https://issues.apache.org/jira/browse/HADOOP-1167
Project: Hadoop
I
[
https://issues.apache.org/jira/browse/HADOOP-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484626
]
Hadoop QA commented on HADOOP-1166:
---
+1, because
http://issues.apache.org/jira/secure/attachment/12354367/h1166.p
[
https://issues.apache.org/jira/browse/HADOOP-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484625
]
Milind Bhandarkar commented on HADOOP-1162:
---
Oh, i misunderstood your question. I am switching buffer seri
[
https://issues.apache.org/jira/browse/HADOOP-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484623
]
Milind Bhandarkar commented on HADOOP-1162:
---
No, I use hex pairs. So, one byte is serialized as two chars
[
https://issues.apache.org/jira/browse/HADOOP-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484622
]
Owen O'Malley commented on HADOOP-1123:
---
+1
> LocalFileSystem gets a NullPointerException when tries to recov
[
https://issues.apache.org/jira/browse/HADOOP-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484617
]
Hadoop QA commented on HADOOP-1159:
---
+1, because
http://issues.apache.org/jira/secure/attachment/12354356/h1159-2
[
https://issues.apache.org/jira/browse/HADOOP-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484611
]
David Bowen commented on HADOOP-1162:
-
Not quite two times, I think. Are you switching to base-64 encoding?
-
[
https://issues.apache.org/jira/browse/HADOOP-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated HADOOP-1166:
--
Attachment: h1166.patch
This patch adds a NullOutputFormat and pulls the code out of RandomWri
[
https://issues.apache.org/jira/browse/HADOOP-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated HADOOP-1166:
--
Status: Patch Available (was: Open)
> Pull the NullOutputFormat into the lib package
> --
[
https://issues.apache.org/jira/browse/HADOOP-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484609
]
David Bowen commented on HADOOP-1163:
-
+1 code reviewed. Looks good.
> Ganglia metrics reporting is misconf
[
https://issues.apache.org/jira/browse/HADOOP-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484608
]
Hadoop QA commented on HADOOP-1164:
---
+1, because
http://issues.apache.org/jira/secure/attachment/12354353/h1164.p
Pull the NullOutputFormat into the lib package
--
Key: HADOOP-1166
URL: https://issues.apache.org/jira/browse/HADOOP-1166
Project: Hadoop
Issue Type: Improvement
Components: mapred
Af
[
https://issues.apache.org/jira/browse/HADOOP-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nigel Daley updated HADOOP-1123:
Status: Patch Available (was: Open)
> LocalFileSystem gets a NullPointerException when tries to r
[
https://issues.apache.org/jira/browse/HADOOP-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nigel Daley updated HADOOP-1123:
Attachment: 1123_with_test.patch
New patch with a test case.
> LocalFileSystem gets a NullPointer
[
https://issues.apache.org/jira/browse/HADOOP-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated HADOOP-1159:
--
Status: Patch Available (was: Open)
> Reducers hang when map output file has a checksum error
[
https://issues.apache.org/jira/browse/HADOOP-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484601
]
Hadoop QA commented on HADOOP-1165:
---
+1, because
http://issues.apache.org/jira/secure/attachment/12354351/jute-pa
[
https://issues.apache.org/jira/browse/HADOOP-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated HADOOP-1159:
--
Attachment: h1159-2.patch
This patch moves the catch of InterruptedException before the catch
[
https://issues.apache.org/jira/browse/HADOOP-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated HADOOP-1164:
--
Status: Patch Available (was: Open)
> TestReplicationPolicy doesn't use port 0 for the NameNo
[
https://issues.apache.org/jira/browse/HADOOP-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated HADOOP-1164:
--
Attachment: h1164.patch
This changes the port to be "0" which causes the system to pick a port
[
https://issues.apache.org/jira/browse/HADOOP-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milind Bhandarkar updated HADOOP-1165:
--
Status: Patch Available (was: In Progress)
> Code for toString in code generated by R
[
https://issues.apache.org/jira/browse/HADOOP-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milind Bhandarkar updated HADOOP-1165:
--
Attachment: jute-patch.txt
Patch attached.
> Code for toString in code generated by R
Code for toString in code generated by Record I/O Compiler can be generic
-
Key: HADOOP-1165
URL: https://issues.apache.org/jira/browse/HADOOP-1165
Project: Hadoop
Issue
[
https://issues.apache.org/jira/browse/HADOOP-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HADOOP-1165 started by Milind Bhandarkar.
> Code for toString in code generated by Record I/O Compiler can be generic
> -
TestReplicationPolicy doesn't use port 0 for the NameNode
-
Key: HADOOP-1164
URL: https://issues.apache.org/jira/browse/HADOOP-1164
Project: Hadoop
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/HADOOP-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated HADOOP-1159:
--
Status: Open (was: Patch Available)
Good catch, Tom. I'll upload a patch shortly.
> Reducers
[
https://issues.apache.org/jira/browse/HADOOP-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484583
]
Michael Bieniosek commented on HADOOP-1081:
---
+1
> JAVA_PLATFORM with spaces (i.e. Mac OS X-ppc-32) breaks
[
https://issues.apache.org/jira/browse/HADOOP-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated HADOOP-1162:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this. Thank
[
https://issues.apache.org/jira/browse/HADOOP-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484577
]
David Bowen commented on HADOOP-1162:
-
+1. Code reviewed and looks fine. A small safe fix.
> Record IO: sear
[
https://issues.apache.org/jira/browse/HADOOP-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated HADOOP-1153:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this. Thank
[
https://issues.apache.org/jira/browse/HADOOP-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484570
]
Tom White commented on HADOOP-1159:
---
By catching Exception, InterruptedException is also caught so it can no longe
[
https://issues.apache.org/jira/browse/HADOOP-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484564
]
Michael Bieniosek commented on HADOOP-1163:
---
My patch (I can't attach in the standard way since this issue
Ganglia metrics reporting is misconfigured
--
Key: HADOOP-1163
URL: https://issues.apache.org/jira/browse/HADOOP-1163
Project: Hadoop
Issue Type: Bug
Components: metrics
Affects Versions:
[
https://issues.apache.org/jira/browse/HADOOP-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484548
]
Raghu Angadi commented on HADOOP-1134:
--
> It's worth noting that, if a .crc file cannot be found for a block, t
[
https://issues.apache.org/jira/browse/HADOOP-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484547
]
Doug Cutting commented on HADOOP-1134:
--
> If source datanode does not check for errors, how would you propose w
[
https://issues.apache.org/jira/browse/HADOOP-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484545
]
Raghu Angadi commented on HADOOP-1134:
--
>> 64KB is only for new blocks.
> I thought we'd benchmark before we c
[
https://issues.apache.org/jira/browse/HADOOP-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484544
]
Doug Cutting commented on HADOOP-1134:
--
> I propose to clearly mark such code as temporary and remove it in nex
[
https://issues.apache.org/jira/browse/HADOOP-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484541
]
Raghu Angadi commented on HADOOP-1134:
--
Upgrade from previous versions requires quite a bit of interaction wit
[
https://issues.apache.org/jira/browse/HADOOP-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484538
]
Doug Cutting commented on HADOOP-1134:
--
> 64KB is only for new blocks.
I thought we'd benchmark before we chan
[
https://issues.apache.org/jira/browse/HADOOP-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484539
]
Arun C Murthy commented on HADOOP-1161:
---
>The alternative is to simply to stall patches that add new features
[
https://issues.apache.org/jira/browse/HADOOP-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484537
]
Hadoop QA commented on HADOOP-1162:
---
+1, because
http://issues.apache.org/jira/secure/attachment/12354338/jute-pa
[
https://issues.apache.org/jira/browse/HADOOP-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nigel Daley updated HADOOP-702:
---
Status: Open (was: Patch Available)
I'll reworking some of the tests to address Owen's concerns.
The
[
https://issues.apache.org/jira/browse/HADOOP-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484530
]
Doug Cutting commented on HADOOP-1161:
--
> I'd strongly vote for a code-freeze [ ... ]
I think "code freeze" mi
[
https://issues.apache.org/jira/browse/HADOOP-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milind Bhandarkar reassigned HADOOP-1162:
-
Assignee: Milind Bhandarkar
> Record IO: seariliizing a byte buffer to CSV fails
[
https://issues.apache.org/jira/browse/HADOOP-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milind Bhandarkar updated HADOOP-1162:
--
Fix Version/s: 0.12.3
Affects Version/s: 0.12.2
Status: Patch Av
[
https://issues.apache.org/jira/browse/HADOOP-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Milind Bhandarkar updated HADOOP-1162:
--
Attachment: jute-patch.txt
This bug also affects the XML serialization of buffers. Thi
Record IO: seariliizing a byte buffer to CSV fails if buffer contains bytes
less than 16.
-
Key: HADOOP-1162
URL: https://issues.apache.org/jira/browse/HADOOP-1162
[
https://issues.apache.org/jira/browse/HADOOP-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Shvachko updated HADOOP-1153:
Status: Patch Available (was: Open)
> DataNode and FSNamesystem don't shutdown cl
[
https://issues.apache.org/jira/browse/HADOOP-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated HADOOP-1130:
--
Status: Open (was: Patch Available)
> Remove unused ClientFinalizer in DFSClient
> --
[
https://issues.apache.org/jira/browse/HADOOP-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484524
]
Milind Bhandarkar commented on HADOOP-1162:
---
I found the bug. It is in Buffer.toString. However, I am in t
[
https://issues.apache.org/jira/browse/HADOOP-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484512
]
dhruba borthakur commented on HADOOP-1153:
--
+1 Code reviewed.
> DataNode and FSNamesystem don't shutdown
[
https://issues.apache.org/jira/browse/HADOOP-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484522
]
Hadoop QA commented on HADOOP-1153:
---
+1, because
http://issues.apache.org/jira/secure/attachment/12354285/Interru
[
https://issues.apache.org/jira/browse/HADOOP-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484500
]
Owen O'Malley commented on HADOOP-1130:
---
Jira keeps eating my comments on this issue. *sigh*
> As hadoop may
[
https://issues.apache.org/jira/browse/HADOOP-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484520
]
Milind Bhandarkar commented on HADOOP-1162:
---
I agree that the unit test needs to be enhanced. However, I h
[
https://issues.apache.org/jira/browse/HADOOP-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484517
]
Arun C Murthy commented on HADOOP-1161:
---
Actually I'd like to propose a small variation of Tom's thoughts:
St
[
https://issues.apache.org/jira/browse/HADOOP-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_1248
]
Hadoop QA commented on HADOOP-1001:
---
+1, because http://issues.apache.org/jira/secure/attachment/12354321/1001.pat
[
https://issues.apache.org/jira/browse/HADOOP-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tahir Hashmi updated HADOOP-1001:
-
Status: Patch Available (was: Open)
> the output of the map is not type checked against the spe
[
https://issues.apache.org/jira/browse/HADOOP-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tahir Hashmi updated HADOOP-1001:
-
Attachment: 1001.patch
Patch to check the type of keys and values generated by the mapper agains
[
https://issues.apache.org/jira/browse/HADOOP-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484431
]
James P. White commented on HADOOP-1161:
Owen said that he thinks bug fixes go on the branches first, which
[
https://issues.apache.org/jira/browse/HADOOP-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484347
]
Tom White commented on HADOOP-1161:
---
+1
Can we take "code freeze" to mean "code freeze in a particular branch"? S
84 matches
Mail list logo
