Re: JCL vs SLF4J

Hi, I didn't follow the whole debate in Hadoop mail list about SLF4J vs JCL so my comment may be irrelevant. However, apart of class loader issues in JCL, did anybody considered performance benefits of SLF4J over JCL? I have switched to SLF4J recently and I found it very handy. Especially the synt

[jira] Updated: (HADOOP-1977) hadoop job -kill , -status causes NullPointerException

[ https://issues.apache.org/jira/browse/HADOOP-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HADOOP-1977: -- Status: Patch Available (was: Open) > hadoop job -kill , -status causes NullPointerException

[jira] Updated: (HADOOP-1977) hadoop job -kill , -status causes NullPointerException

[ https://issues.apache.org/jira/browse/HADOOP-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HADOOP-1977: -- Attachment: NPEinJobClient_v1.hadoop-0.14.patch Previous patch was against trunk, this one is

[jira] Updated: (HADOOP-1977) hadoop job -kill , -status causes NullPointerException

[ https://issues.apache.org/jira/browse/HADOOP-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar updated HADOOP-1977: -- Attachment: NPEinJobClient_v1.patch The problem is ındeed in the JobConf initialization. The p

[jira] Updated: (HADOOP-1857) Ability to run a script when a task fails to capture stack traces

[ https://issues.apache.org/jira/browse/HADOOP-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Devaraj Das updated HADOOP-1857: Status: Open (was: Patch Available) Could you please check why core-tests are failing with this p

[jira] Assigned: (HADOOP-1977) hadoop job -kill , -status causes NullPointerException

[ https://issues.apache.org/jira/browse/HADOOP-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Enis Soztutar reassigned HADOOP-1977: - Assignee: Enis Soztutar > hadoop job -kill , -status causes NullPointerException > -

[jira] Commented: (HADOOP-1972) LzoCompressor.finished doesn't check whether the user actually wants to finish compressing

[ https://issues.apache.org/jira/browse/HADOOP-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531692 ] Devaraj Das commented on HADOOP-1972: - +1 > LzoCompressor.finished doesn't check whether the user actually want

[jira] Created: (HADOOP-1983) jobs using pipes interface with tasks not using java output format have a good chance of not updating progress and timing out

jobs using pipes interface with tasks not using java output format have a good chance of not updating progress and timing out - Key: HADOOP-1983

[jira] Created: (HADOOP-1982) TaskTracker provided java.library.path is lost if set in the job.xml

TaskTracker provided java.library.path is lost if set in the job.xml Key: HADOOP-1982 URL: https://issues.apache.org/jira/browse/HADOOP-1982 Project: Hadoop Issue Type: Bug

[jira] Created: (HADOOP-1981) Need to document the controls for sorting and grouping into the reduce

Need to document the controls for sorting and grouping into the reduce -- Key: HADOOP-1981 URL: https://issues.apache.org/jira/browse/HADOOP-1981 Project: Hadoop Issue Type:

[jira] Commented: (HADOOP-1960) [hbase] If a region server cannot talk to the master after several attempts, it should shut itself down

[ https://issues.apache.org/jira/browse/HADOOP-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531678 ] Hadoop QA commented on HADOOP-1960: --- -1 overall. Here are the results of testing the latest attachment http://is

[jira] Resolved: (HADOOP-1969) org.apache.hadoop.io.Text uses static ChasetDecoders, but they aren't thread-safe

[ https://issues.apache.org/jira/browse/HADOOP-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Evans resolved HADOOP-1969. - Resolution: Invalid I looked into this and the access to the decoder and encoder is synchronized

[jira] Updated: (HADOOP-1955) Corrupted block replication retries for ever

[ https://issues.apache.org/jira/browse/HADOOP-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raghu Angadi updated HADOOP-1955: - Attachment: HADOOP-1955.patch When NameNode is not heavily loaded, each time {{computeDatanodeW

[jira] Created: (HADOOP-1980) 'dfsadmin -safemode enter' should prevent the namenode from leaving safemode automatically after startup

'dfsadmin -safemode enter' should prevent the namenode from leaving safemode automatically after startup Key: HADOOP-1980 URL: https://issues.apache.org/jira/

[jira] Updated: (HADOOP-1960) [hbase] If a region server cannot talk to the master after several attempts, it should shut itself down

[ https://issues.apache.org/jira/browse/HADOOP-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Kellerman updated HADOOP-1960: -- Status: Patch Available (was: In Progress) Works locally. Try Hudson. > [hbase] If a region

[jira] Updated: (HADOOP-1960) [hbase] If a region server cannot talk to the master after several attempts, it should shut itself down

[ https://issues.apache.org/jira/browse/HADOOP-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Kellerman updated HADOOP-1960: -- Attachment: patch.txt TestMasterAbort - New test MiniHBaseCluster - Add getter that returns t

[jira] Created: (HADOOP-1979) fsck on namenode without datanodes takes too much time

fsck on namenode without datanodes takes too much time -- Key: HADOOP-1979 URL: https://issues.apache.org/jira/browse/HADOOP-1979 Project: Hadoop Issue Type: Bug Components: dfs

[jira] Commented: (HADOOP-1942) Increase the concurrency of transaction logging to edits log

[ https://issues.apache.org/jira/browse/HADOOP-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531657 ] Raghu Angadi commented on HADOOP-1942: -- > I am thinking of extending your idea to remember the counter in logEd

[jira] Commented: (HADOOP-1955) Corrupted block replication retries for ever

[ https://issues.apache.org/jira/browse/HADOOP-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531656 ] Raghu Angadi commented on HADOOP-1955: -- Even in my dev set up, Namenode always asks the same datanode to repli

[jira] Commented: (HADOOP-1942) Increase the concurrency of transaction logging to edits log

[ https://issues.apache.org/jira/browse/HADOOP-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531655 ] dhruba borthakur commented on HADOOP-1942: -- I like your idea. In fact, the current code has a bug that the

[jira] Updated: (HADOOP-1948) Spurious error message during block crc upgrade.

[ https://issues.apache.org/jira/browse/HADOOP-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HADOOP-1948: - Resolution: Fixed Fix Version/s: 0.15.0 Status: Resolved (was: Patch A

[jira] Commented: (HADOOP-1914) HDFS should have a NamenodeProtocol to allow secondary namenodes and rebalancing processes to communicate with a primary namenode

[ https://issues.apache.org/jira/browse/HADOOP-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531648 ] Hadoop QA commented on HADOOP-1914: --- +1 overall. Here are the results of testing the latest attachment http://is

[jira] Updated: (HADOOP-1914) HDFS should have a NamenodeProtocol to allow secondary namenodes and rebalancing processes to communicate with a primary namenode

[ https://issues.apache.org/jira/browse/HADOOP-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hairong Kuang updated HADOOP-1914: -- Attachment: namenodeProtocol3.patch > HDFS should have a NamenodeProtocol to allow secondary

[jira] Updated: (HADOOP-1914) HDFS should have a NamenodeProtocol to allow secondary namenodes and rebalancing processes to communicate with a primary namenode

[ https://issues.apache.org/jira/browse/HADOOP-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hairong Kuang updated HADOOP-1914: -- Status: Open (was: Patch Available) > HDFS should have a NamenodeProtocol to allow secondary

[jira] Updated: (HADOOP-1914) HDFS should have a NamenodeProtocol to allow secondary namenodes and rebalancing processes to communicate with a primary namenode

[ https://issues.apache.org/jira/browse/HADOOP-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hairong Kuang updated HADOOP-1914: -- Status: Patch Available (was: Open) > HDFS should have a NamenodeProtocol to allow secondary

[jira] Work started: (HADOOP-1960) [hbase] If a region server cannot talk to the master after several attempts, it should shut itself down

[ https://issues.apache.org/jira/browse/HADOOP-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HADOOP-1960 started by Jim Kellerman. > [hbase] If a region server cannot talk to the master after several attempts, > it should shut itself down >

Hadoop 0.14.2 release

Hi, There are 8 open blockers (3 with patch available) targeted for 0.14.2. Can we get the blockers resolved by Wed (Oct 3) so we can wrap up the release, barring any new issues? Thanks, Mukund (Works for Nigel)

[jira] Commented: (HADOOP-1955) Corrupted block replication retries for ever

[ https://issues.apache.org/jira/browse/HADOOP-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531628 ] Raghu Angadi commented on HADOOP-1955: -- For 0.14.x, I will implement using different source replica for differe

[jira] Commented: (HADOOP-1914) HDFS should have a NamenodeProtocol to allow secondary namenodes and rebalancing processes to communicate with a primary namenode

[ https://issues.apache.org/jira/browse/HADOOP-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531627 ] Hadoop QA commented on HADOOP-1914: --- -1 overall. Here are the results of testing the latest attachment http://is

[jira] Commented: (HADOOP-1978) Name-node should remove edits.new during startup rather than renaming it to edits.

[ https://issues.apache.org/jira/browse/HADOOP-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531626 ] Doug Cutting commented on HADOOP-1978: -- > Does it mean that we need a fix for 0.13 release too? I don't think

[jira] Commented: (HADOOP-1977) hadoop job -kill , -status causes NullPointerException

[ https://issues.apache.org/jira/browse/HADOOP-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531624 ] Raghu Angadi commented on HADOOP-1977: -- > It would be nice to have a version of the CLI parsing library that wa

[jira] Commented: (HADOOP-1978) Name-node should remove edits.new during startup rather than renaming it to edits.

[ https://issues.apache.org/jira/browse/HADOOP-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531622 ] dhruba borthakur commented on HADOOP-1978: -- This bug was introduced in 0.13. Does it mean that we need a fi

[jira] Created: (HADOOP-1978) Name-node should remove edits.new during startup rather than renaming it to edits.

Name-node should remove edits.new during startup rather than renaming it to edits. -- Key: HADOOP-1978 URL: https://issues.apache.org/jira/browse/HADOOP-1978 Project: Had

[jira] Commented: (HADOOP-1977) hadoop job -kill , -status causes NullPointerException

[ https://issues.apache.org/jira/browse/HADOOP-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531615 ] Owen O'Malley commented on HADOOP-1977: --- I looked at this problem. It stems from the fact that JobClient creat

[jira] Commented: (HADOOP-1955) Corrupted block replication retries for ever

[ https://issues.apache.org/jira/browse/HADOOP-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531613 ] Raghu Angadi commented on HADOOP-1955: -- Koji, did the work around help? I would like to know if asking differen

[jira] Updated: (HADOOP-1975) hbase tests failing with java.lang.NumberFormatException

[ https://issues.apache.org/jira/browse/HADOOP-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Kellerman updated HADOOP-1975: -- Resolution: Fixed Status: Resolved (was: Patch Available) Tests passed. Committed. >

[jira] Commented: (HADOOP-1975) hbase tests failing with java.lang.NumberFormatException

[ https://issues.apache.org/jira/browse/HADOOP-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531606 ] Hadoop QA commented on HADOOP-1975: --- +1 overall. Here are the results of testing the latest attachment http://is

[jira] Commented: (HADOOP-1851) Map output compression codec cannot be set independently of job output compression codec

[ https://issues.apache.org/jira/browse/HADOOP-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531604 ] Doug Cutting commented on HADOOP-1851: -- Renaming mapred.compress.map.output is not back-compatible. Perhaps we

[jira] Updated: (HADOOP-1914) HDFS should have a NamenodeProtocol to allow secondary namenodes and rebalancing processes to communicate with a primary namenode

[ https://issues.apache.org/jira/browse/HADOOP-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hairong Kuang updated HADOOP-1914: -- Status: Open (was: Patch Available) > HDFS should have a NamenodeProtocol to allow secondary

[jira] Updated: (HADOOP-1914) HDFS should have a NamenodeProtocol to allow secondary namenodes and rebalancing processes to communicate with a primary namenode

[ https://issues.apache.org/jira/browse/HADOOP-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hairong Kuang updated HADOOP-1914: -- Status: Patch Available (was: Open) > HDFS should have a NamenodeProtocol to allow secondary

[jira] Updated: (HADOOP-1914) HDFS should have a NamenodeProtocol to allow secondary namenodes and rebalancing processes to communicate with a primary namenode

[ https://issues.apache.org/jira/browse/HADOOP-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hairong Kuang updated HADOOP-1914: -- Attachment: namenodeProtocol2.patch > HDFS should have a NamenodeProtocol to allow secondary

[jira] Updated: (HADOOP-1977) hadoop job -kill , -status causes NullPointerException

[ https://issues.apache.org/jira/browse/HADOOP-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lohit vijayarenu updated HADOOP-1977: - Component/s: mapred Summary: hadoop job -kill , -status causes NullPointerExcepti

[jira] Updated: (HADOOP-1977) hadoop job -kill , -status causes NullPointerException

[ https://issues.apache.org/jira/browse/HADOOP-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lohit vijayarenu updated HADOOP-1977: - Priority: Blocker (was: Major) > hadoop job -kill , -status causes NullPointerException

[jira] Created: (HADOOP-1977) hadoop job -kill , -status

hadoop job -kill , -status --- Key: HADOOP-1977 URL: https://issues.apache.org/jira/browse/HADOOP-1977 Project: Hadoop Issue Type: Bug Affects Versions: 0.14.1 Reporter: lohit vijayarenu

[jira] Commented: (HADOOP-1963) Code contribution of Kosmos Filesystem implementation of Hadoop Filesystem interface

[ https://issues.apache.org/jira/browse/HADOOP-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531598 ] Doug Cutting commented on HADOOP-1963: -- I agree with Nigel. Core code should have unit tests. Without these,

Re: JCL vs SLF4J

Michael Stack wrote: Doug Cutting wrote: I have used the JVM's built-in logging and found it lacking. Do you remember what the holes in JUL were? Sorry, I don't remember all the details. I note that Hadoop uses log4j's DailyRollingFileAppender, and nothing like that is present in JUL. And

[jira] Commented: (HADOOP-1963) Code contribution of Kosmos Filesystem implementation of Hadoop Filesystem interface

[ https://issues.apache.org/jira/browse/HADOOP-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531595 ] Nigel Daley commented on HADOOP-1963: - I think the package.html should go in the src/java/org/apache/hadoop/fs/k

Re: [jira] Commented: (HADOOP-1973) NPE at JobTracker startup..

Sorry.. this was on trunk. -G. Owen O'Malley (JIRA) wrote: [ https://issues.apache.org/jira/browse/HADOOP-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531583 ] Owen O'Malley commented on HADOOP-1973: --- Gautam, we

[jira] Commented: (HADOOP-1857) Ability to run a script when a task fails to capture stack traces

[ https://issues.apache.org/jira/browse/HADOOP-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531589 ] Hadoop QA commented on HADOOP-1857: --- -1 overall. Here are the results of testing the latest attachment http://is

Re: JCL vs SLF4J

Doug Cutting wrote: I have used the JVM's built-in logging and found it lacking. Do you remember what the holes in JUL were? Hadoop needed the extra facility provided by log4j's PatternLayout or it needed some of the more exotic appenders? Or was it something else? (I don't see anything in a

[jira] Commented: (HADOOP-1966) [hbase] TestDFSAbort failed in nightly #253

[ https://issues.apache.org/jira/browse/HADOOP-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531587 ] Hudson commented on HADOOP-1966: Integrated in Hadoop-Nightly #256 (See [http://lucene.zones.apache.org:8080/hudson

Build failed in Hudson: Hadoop-Nightly #256

See http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/256/changes Changes: [dhruba] HADOOP-1708. Make files appear in namespace as soon as they are created. This should appear in the "INCOMPATIBLE" section in the release notes rather than in the "NEW FEATURES" section. (Dhruba Borth

[jira] Commented: (HADOOP-1935) NullPointerException in internalReleaseCreate

[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531584 ] Hudson commented on HADOOP-1935: Integrated in Hadoop-Nightly #256 (See [http://lucene.zones.apache.org:8080/hudson

[jira] Commented: (HADOOP-1820) [hbase] regionserver creates hlogs without bound

[ https://issues.apache.org/jira/browse/HADOOP-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531585 ] Hudson commented on HADOOP-1820: Integrated in Hadoop-Nightly #256 (See [http://lucene.zones.apache.org:8080/hudson

[jira] Commented: (HADOOP-1708) make files visible in the namespace as soon as they are created

[ https://issues.apache.org/jira/browse/HADOOP-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531586 ] Hudson commented on HADOOP-1708: Integrated in Hadoop-Nightly #256 (See [http://lucene.zones.apache.org:8080/hudson

[jira] Commented: (HADOOP-1973) NPE at JobTracker startup..

[ https://issues.apache.org/jira/browse/HADOOP-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531583 ] Owen O'Malley commented on HADOOP-1973: --- Gautam, were you running 0.14 or pre-0.15 when this happened? > NPE

[jira] Updated: (HADOOP-1946) du should be not called on every heartbeat

[ https://issues.apache.org/jira/browse/HADOOP-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HADOOP-1946: - Resolution: Fixed Status: Resolved (was: Patch Available) I just committed this

[jira] Commented: (HADOOP-1975) hbase tests failing with java.lang.NumberFormatException

[ https://issues.apache.org/jira/browse/HADOOP-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531580 ] Jim Kellerman commented on HADOOP-1975: --- I found a machine on which I could reproduce the error. The submitte

[jira] Updated: (HADOOP-1975) hbase tests failing with java.lang.NumberFormatException

[ https://issues.apache.org/jira/browse/HADOOP-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Kellerman updated HADOOP-1975: -- Fix Version/s: 0.15.0 Affects Version/s: 0.15.0 Status: Patch Available

[jira] Updated: (HADOOP-1975) hbase tests failing with java.lang.NumberFormatException

[ https://issues.apache.org/jira/browse/HADOOP-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Kellerman updated HADOOP-1975: -- Attachment: patch.txt Although I have not seen this error in the environments I work in, I bel

Re: svn commit: r580872 - /lucene/hadoop/trunk/CHANGES.txt

[EMAIL PROTECTED] wrote: INCOMPATIBLE CHANGES +HADOOP-1708. Make files appear in namespace as soon as they are +created. (Dhruba Borthakur via dhruba) + HADOOP-999. A HDFS Client immediately informs the NameNode of a new file creation. ClientProtocol version changed fr

[jira] Commented: (HADOOP-1969) org.apache.hadoop.io.Text uses static ChasetDecoders, but they aren't thread-safe

[ https://issues.apache.org/jira/browse/HADOOP-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531570 ] Doug Cutting commented on HADOOP-1969: -- Perhaps this should use a static ThreadLocal instead, so that encoders

Re: JCL vs SLF4J

Eric Baldeschwieler wrote: I find our current use of apache commons while depending on specific features of log4j awkward. Yes, this isn't ideal, but an advantage is that, should we switch to a different backend, we only need change the few log4j-specific bits, and not every line that logs so

[jira] Commented: (HADOOP-1851) Map output compression codec cannot be set independently of job output compression codec

[ https://issues.apache.org/jira/browse/HADOOP-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531551 ] Hadoop QA commented on HADOOP-1851: --- -1 overall. Here are the results of testing the latest attachment http://is

[jira] Commented: (HADOOP-1975) hbase tests failing with java.lang.NumberFormatException

[ https://issues.apache.org/jira/browse/HADOOP-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531550 ] Jim Kellerman commented on HADOOP-1975: --- In what environment are you seeing this problem? I looked at the bui

[jira] Assigned: (HADOOP-1975) hbase tests failing with java.lang.NumberFormatException

[ https://issues.apache.org/jira/browse/HADOOP-1975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Kellerman reassigned HADOOP-1975: - Assignee: Jim Kellerman > hbase tests failing with java.lang.NumberFormatException > --

[jira] Created: (HADOOP-1976) Show data locality as % and reflect it in the map graph.

Show data locality as % and reflect it in the map graph. - Key: HADOOP-1976 URL: https://issues.apache.org/jira/browse/HADOOP-1976 Project: Hadoop Issue Type: Improvement Affects V

[jira] Updated: (HADOOP-1974) Progress node should cache root object for faster progress computation

[ https://issues.apache.org/jira/browse/HADOOP-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratan updated HADOOP-1974: Attachment: 1974_patch01 >From my comments in HADOOP_1970: There are 2-3 methods that traverse t

[jira] Updated: (HADOOP-1970) tasktracker hang in reduce. Deadlock between main and comm thread

[ https://issues.apache.org/jira/browse/HADOOP-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratan updated HADOOP-1970: Attachment: 1970_patch02 Since this is a fix for 0.14.2, and I shouldn't be adding any new functi

[jira] Commented: (HADOOP-1857) Ability to run a script when a task fails to capture stack traces

[ https://issues.apache.org/jira/browse/HADOOP-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531460 ] Amareshwari Sri Ramadasu commented on HADOOP-1857: -- All this documentation will be part of Overall

[jira] Created: (HADOOP-1975) hbase tests failing with java.lang.NumberFormatException

hbase tests failing with java.lang.NumberFormatException - Key: HADOOP-1975 URL: https://issues.apache.org/jira/browse/HADOOP-1975 Project: Hadoop Issue Type: Bug Components:

[jira] Updated: (HADOOP-1973) NPE at JobTracker startup..

[ https://issues.apache.org/jira/browse/HADOOP-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gautam Kowshik updated HADOOP-1973: --- Description: At JT startup a bunch of these were thrown.. and the JT shutdown. 2007-10-01

[jira] Created: (HADOOP-1974) Progress node should cache root object for faster progress computation

Progress node should cache root object for faster progress computation -- Key: HADOOP-1974 URL: https://issues.apache.org/jira/browse/HADOOP-1974 Project: Hadoop Issue Type:

[jira] Commented: (HADOOP-1857) Ability to run a script when a task fails to capture stack traces

[ https://issues.apache.org/jira/browse/HADOOP-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531456 ] Amareshwari Sri Ramadasu commented on HADOOP-1857: -- Usage Documentation : A facility is provided,

[jira] Created: (HADOOP-1973) NPE at JobTracker startup..

NPE at JobTracker startup.. --- Key: HADOOP-1973 URL: https://issues.apache.org/jira/browse/HADOOP-1973 Project: Hadoop Issue Type: Bug Components: mapred Affects Versions: 0.14.1 Reporter: G

[jira] Updated: (HADOOP-1857) Ability to run a script when a task fails to capture stack traces

[ https://issues.apache.org/jira/browse/HADOOP-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amareshwari Sri Ramadasu updated HADOOP-1857: - Status: Patch Available (was: Open) After incorporating comments on thi

[jira] Updated: (HADOOP-1857) Ability to run a script when a task fails to capture stack traces

[ https://issues.apache.org/jira/browse/HADOOP-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amareshwari Sri Ramadasu updated HADOOP-1857: - Attachment: patch-1857.txt > Ability to run a script when a task fails t

[jira] Updated: (HADOOP-1857) Ability to run a script when a task fails to capture stack traces

[ https://issues.apache.org/jira/browse/HADOOP-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amareshwari Sri Ramadasu updated HADOOP-1857: - Attachment: (was: patch1857.txt) > Ability to run a script when a ta

[jira] Updated: (HADOOP-1857) Ability to run a script when a task fails to capture stack traces

[ https://issues.apache.org/jira/browse/HADOOP-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amareshwari Sri Ramadasu updated HADOOP-1857: - Attachment: patch1857.txt > Ability to run a script when a task fails to

[jira] Updated: (HADOOP-1970) tasktracker hang in reduce. Deadlock between main and comm thread

[ https://issues.apache.org/jira/browse/HADOOP-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratan updated HADOOP-1970: Attachment: 1970_patch01 Well, it's a little bigger than that. What's happening is that there are

[jira] Commented: (HADOOP-89) files are not visible until they are closed

[ https://issues.apache.org/jira/browse/HADOOP-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531423 ] dhruba borthakur commented on HADOOP-89: It is actually HADOOP-1708 that introduced the feature that "files ap

[jira] Updated: (HADOOP-1935) NullPointerException in internalReleaseCreate

[ https://issues.apache.org/jira/browse/HADOOP-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HADOOP-1935: - Resolution: Fixed Status: Resolved (was: Patch Available) I just submitted this