[
https://issues.apache.org/jira/browse/HADOOP-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-5529:
-
Attachment: HADOOP-5529.patch
New status object is replaced in map. This quick patch
: Bug
Components: mapred
Affects Versions: 0.15.3
Reporter: Lohit Vijayarenu
Priority: Minor
In some cases, Task diagnostic message are received out of order of the actual
failed report. In such cases, loging of failed task to history file might skip
logging the previ
[
https://issues.apache.org/jira/browse/HADOOP-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681137#action_12681137
]
Lohit Vijayarenu commented on HADOOP-5467:
--
+1 it would be very helpful.
[
https://issues.apache.org/jira/browse/HADOOP-5422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu resolved HADOOP-5422.
--
Resolution: Invalid
What seem to happen here is that
{noformat}
hadoop dfs -lsr
[
https://issues.apache.org/jira/browse/HADOOP-5331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-5331:
-
Status: Patch Available (was: Open)
resubmitting patch since it was not picked up by
[
https://issues.apache.org/jira/browse/HADOOP-5331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-5331:
-
Status: Open (was: Patch Available)
> KFS: Add support for app
files and also running fsck programatically. If you would want to test
something, you make the changes and run the test. You could also run just one
test alone by executing
'ant -Dtestcase=TestFsck test'
Lohit
- Original Message
From: Ajit Ratnaparkhi
To: core-dev@hadoop.
with different conf directory containing different
conf file
Lohit
- Original Message
From: Ajit Ratnaparkhi
To: core-dev@hadoop.apache.org
Sent: Wednesday, February 25, 2009 11:04:15 PM
Subject: multiple datanodes on single node cluster
Hi all,
Is it possible to run multiple
[
https://issues.apache.org/jira/browse/HADOOP-5331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-5331:
-
Status: Patch Available (was: Open)
> KFS: Add support for app
[
https://issues.apache.org/jira/browse/HADOOP-5331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-5331:
-
Status: Open (was: Patch Available)
> KFS: Add support for app
[
https://issues.apache.org/jira/browse/HADOOP-5331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-5331:
-
Assignee: Sriram Rao
Status: Patch Available (was: Open)
Looks good. Submitting
[
https://issues.apache.org/jira/browse/HADOOP-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-5292:
-
Resolution: Fixed
Fix Version/s: (was: 0.19.1)
0.20.0
[
https://issues.apache.org/jira/browse/HADOOP-5292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-5292:
-
Assignee: Sriram Rao
+1 Looks good.
> KFS: calling getFileBlockLocations() on 0-len
[
https://issues.apache.org/jira/browse/HADOOP-3741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-3741:
-
Assignee: Tsz Wo (Nicholas), SZE
Hadoop Flags: [Reviewed]
+1. This looks good
[
https://issues.apache.org/jira/browse/HADOOP-4826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655783#action_12655783
]
Lohit Vijayarenu commented on HADOOP-4826:
--
This looks good. One minor com
: 0.20.0
Environment: All
Reporter: Lohit Vijayarenu
Priority: Minor
hadoop fsck / would check state of entire filesystem. It would be good to have
an option to ignore lost+found directory. Better yet, a way to specify ignore
list.
--
This message is automatically
[
https://issues.apache.org/jira/browse/HADOOP-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652867#action_12652867
]
Lohit Vijayarenu commented on HADOOP-4761:
--
>Also, an utility to check
Hello,
Is there an easy way to get Reduce Output Bytes?
Thanks,
Lohit
[
https://issues.apache.org/jira/browse/HADOOP-4697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-4697:
-
Affects Version/s: (was: 0.17.0)
0.18.0
Hadoop Flags
Components: fs
Affects Versions: 0.17.0
Environment: Hadoop on KFS
Reporter: Lohit Vijayarenu
Assignee: Sriram Rao
Fix For: 0.19.1
getBlockLocations() on KFS fail with the following stack trace for large files
(with multiple blocks
Hi Ankur,
We have had this kind of failure reported by others earlier on this list.
This might help you
http://markmail.org/message/u6l6lwus33oeivcd
Thanks,
Lohit
- Original Message
From: ANKUR GOEL <[EMAIL PROTECTED]>
To: core-dev@hadoop.apache.org; [EMAIL PROTECTED]
Sent: Th
[
https://issues.apache.org/jira/browse/HADOOP-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646715#action_12646715
]
Lohit Vijayarenu commented on HADOOP-3923:
--
Ok, if more servlets are adde
[
https://issues.apache.org/jira/browse/HADOOP-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646658#action_12646658
]
Lohit Vijayarenu commented on HADOOP-3923:
--
Would it be better to
[
https://issues.apache.org/jira/browse/HADOOP-4285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634921#action_12634921
]
Lohit Vijayarenu commented on HADOOP-4285:
--
bq. what do you mean by cur
Components: mapred
Affects Versions: 0.20.0
Reporter: Lohit Vijayarenu
Priority: Minor
It would be good to have tasks know its current working directory via JobConf,
instead of deriving the same or trying to get local current working directory.
I see that we already derive
their state.
Lohit
On Sep 25, 2008, at 6:17 PM, "Edward J. Yoon" <[EMAIL PROTECTED]> wrote:
The name node safe mode means that the name node is not changing the
state of the
file system. Meta data is read-only, and block replication / removal
is not taking place.
On Fri, Sep 26, 200
[
https://issues.apache.org/jira/browse/HADOOP-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634257#action_12634257
]
Lohit Vijayarenu commented on HADOOP-4234:
--
bq. The change comment for
[
https://issues.apache.org/jira/browse/HADOOP-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu resolved HADOOP-4245.
--
Resolution: Fixed
Fix Version/s: (was: 0.19.0)
0.20.0
[
https://issues.apache.org/jira/browse/HADOOP-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634227#action_12634227
]
Lohit Vijayarenu commented on HADOOP-4245:
--
This was tested locally. I ran t
[
https://issues.apache.org/jira/browse/HADOOP-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634221#action_12634221
]
Lohit Vijayarenu commented on HADOOP-4234:
--
contrib test failure is tracke
[
https://issues.apache.org/jira/browse/HADOOP-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-4234:
-
Affects Version/s: 0.19.0
> KFS: Allow KFS layer to interface with multiple
[
https://issues.apache.org/jira/browse/HADOOP-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-4234:
-
Resolution: Fixed
Fix Version/s: (was: 0.19.0)
0.20.0
[
https://issues.apache.org/jira/browse/HADOOP-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-4234:
-
Status: Open (was: Patch Available)
> KFS: Allow KFS layer to interface with multi
[
https://issues.apache.org/jira/browse/HADOOP-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-4234:
-
Status: Patch Available (was: Open)
> KFS: Allow KFS layer to interface with multi
[
https://issues.apache.org/jira/browse/HADOOP-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-4234:
-
Status: Open (was: Patch Available)
> KFS: Allow KFS layer to interface with multi
[
https://issues.apache.org/jira/browse/HADOOP-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-4234:
-
Status: Patch Available (was: Open)
> KFS: Allow KFS layer to interface with multi
[
https://issues.apache.org/jira/browse/HADOOP-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu resolved HADOOP-3354.
--
Resolution: Cannot Reproduce
Agree with Nicolas. We haven't seen this for a
[
https://issues.apache.org/jira/browse/HADOOP-4234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633444#action_12633444
]
Lohit Vijayarenu commented on HADOOP-4234:
--
+1 Looks good.
> KFS: Al
[
https://issues.apache.org/jira/browse/HADOOP-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-3911:
-
Resolution: Fixed
Fix Version/s: 0.19.0
Release Note: Add a check to fsck
[
https://issues.apache.org/jira/browse/HADOOP-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-4155:
-
Resolution: Fixed
Fix Version/s: 0.19.0
Hadoop Flags: [Reviewed
[
https://issues.apache.org/jira/browse/HADOOP-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630738#action_12630738
]
lohit edited comment on HADOOP-3911 at 9/13/08 1:1
[
https://issues.apache.org/jira/browse/HADOOP-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-3911:
-
Status: Patch Available (was: Reopened)
> ' -blocks ' option not bei
[
https://issues.apache.org/jira/browse/HADOOP-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-3911:
-
Attachment: HADOOP-3911.patch
This was not happenning in 0.18 becuase
[
https://issues.apache.org/jira/browse/HADOOP-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630436#action_12630436
]
Lohit Vijayarenu commented on HADOOP-4159:
--
Thanks Nicolas, looks likes on
[
https://issues.apache.org/jira/browse/HADOOP-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu reassigned HADOOP-4155:
Assignee: Lohit Vijayarenu
> JobHisotry::JOBTRACKER_START_TIME is not initiali
[
https://issues.apache.org/jira/browse/HADOOP-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu reassigned HADOOP-4159:
Assignee: Lohit Vijayarenu
> jobdetails.jsp could show analysejobhistory.
[
https://issues.apache.org/jira/browse/HADOOP-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-4159:
-
Status: Patch Available (was: Open)
> jobdetails.jsp could show analysejobhistory.
[
https://issues.apache.org/jira/browse/HADOOP-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-4159:
-
Attachment: HADOOP-4159.patch
small additional, but I feel would be good info to have
Issue Type: Improvement
Components: mapred
Reporter: Lohit Vijayarenu
Priority: Trivial
It would be good to have analysejobhistory details shown on jobdetails.jsp for
successfully completed jobs.
--
This message is automatically generated by JIRA
[
https://issues.apache.org/jira/browse/HADOOP-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-4155:
-
Status: Patch Available (was: Open)
Thanks Amareshwari, making it PA
> JobHiso
[
https://issues.apache.org/jira/browse/HADOOP-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-4155:
-
Attachment: HADOOP-4155.patch
Attached patch changes this. No tests as this just
Reporter: Lohit Vijayarenu
JobHistory::JOBTRACKER_START_TIME seems to be initalize to current time. I
think it should be initialized to current jobtracker's start time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/HADOOP-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630052#action_12630052
]
Lohit Vijayarenu commented on HADOOP-4155:
--
I am trying to link 'Analyz
I might be wrong but my guess is this. This exception might be from the
underneath layer of dfs. Output creates a file and in your case there might me
multiple create requests. Can your threads share output collector?
Sent from my iPhone
On Sep 8, 2008, at 12:51 AM, "Goel, Ankur" <[EMAIL PROTE
[
https://issues.apache.org/jira/browse/HADOOP-3968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-3968:
-
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch
[
https://issues.apache.org/jira/browse/HADOOP-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-4078:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed
[
https://issues.apache.org/jira/browse/HADOOP-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628805#action_12628805
]
Lohit Vijayarenu commented on HADOOP-3874:
--
Saw another failure for this
[
https://issues.apache.org/jira/browse/HADOOP-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-4078:
-
Status: Patch Available (was: Open)
> TestKosmosFileSystem fails on tr
[
https://issues.apache.org/jira/browse/HADOOP-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-4078:
-
Status: Open (was: Patch Available)
> TestKosmosFileSystem fails on tr
[
https://issues.apache.org/jira/browse/HADOOP-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-4078:
-
Attachment: HADOOP-4078.patch
Good catch, multiple machines, multiple patches. This one
[
https://issues.apache.org/jira/browse/HADOOP-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-4078:
-
Status: Patch Available (was: Open)
> TestKosmosFileSystem fails on tr
[
https://issues.apache.org/jira/browse/HADOOP-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628777#action_12628777
]
Lohit Vijayarenu commented on HADOOP-4078:
--
Thanks Nicholas for testing thi
[
https://issues.apache.org/jira/browse/HADOOP-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-4078:
-
Attachment: HADOOP-4078.patch
When the full test suite is run, this fails becuase of
[
https://issues.apache.org/jira/browse/HADOOP-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628676#action_12628676
]
Lohit Vijayarenu commented on HADOOP-4078:
--
I am unable to reproduce this on
[
https://issues.apache.org/jira/browse/HADOOP-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-4069:
-
Status: Patch Available (was: Open)
> TestKosmosFileSystem can fail when run thro
[
https://issues.apache.org/jira/browse/HADOOP-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-4069:
-
Attachment: HADOOP-4069.patch
Like other test cases, it would be good to create baseDir
[
https://issues.apache.org/jira/browse/HADOOP-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-3948:
-
Affects Version/s: 0.19.0
Fix Version/s: 0.19.0
> Separate Namenodes edits
[
https://issues.apache.org/jira/browse/HADOOP-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627116#action_12627116
]
Lohit Vijayarenu commented on HADOOP-3948:
--
Passes all test-patch and all t
[
https://issues.apache.org/jira/browse/HADOOP-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu reassigned HADOOP-3948:
Assignee: Lohit Vijayarenu
> Separate Namenodes edits and fsim
[
https://issues.apache.org/jira/browse/HADOOP-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-3948:
-
Status: Patch Available (was: Open)
> Separate Namenodes edits and fsim
[
https://issues.apache.org/jira/browse/HADOOP-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-3948:
-
Attachment: HADOOP-3948.patch
Thanks Konstantin. Updated patch with all your inputs
[
https://issues.apache.org/jira/browse/HADOOP-4045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626868#action_12626868
]
Lohit Vijayarenu commented on HADOOP-4045:
--
It would be good to see if we
Affects Versions: 0.19.0
Reporter: Lohit Vijayarenu
Fix For: 0.19.0
In _FSEditLog::rollEdits_, if we encounter an error during opening edits.new,
we remove the store directory associated with it. At this point we should also
increment checkpoint on all other
[
https://issues.apache.org/jira/browse/HADOOP-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-3948:
-
Attachment: HADOOP-3948.patch
Updated patch fixing findbugs warnings. Also added few
[
https://issues.apache.org/jira/browse/HADOOP-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-3966:
-
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch
[
https://issues.apache.org/jira/browse/HADOOP-3966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-3966:
-
Affects Version/s: 0.18.0
> Place the new findbugs warnings introduced by the patch
[
https://issues.apache.org/jira/browse/HADOOP-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-3948:
-
Attachment: HADOOP-3948.patch
Attached patch removes FSImage::processIOError
[
https://issues.apache.org/jira/browse/HADOOP-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626201#action_12626201
]
Lohit Vijayarenu commented on HADOOP-4037:
--
+1
> HadoopQA contrib -1 c
[
https://issues.apache.org/jira/browse/HADOOP-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-3948:
-
Attachment: HADOOP-3948.patch
Updated patch, tested manually different directory
[
https://issues.apache.org/jira/browse/HADOOP-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-3742:
-
Assignee: Sanjay Radia
Status: Patch Available (was: Open)
> Clean up javadoc
[
https://issues.apache.org/jira/browse/HADOOP-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624985#action_12624985
]
Lohit Vijayarenu commented on HADOOP-3742:
--
+1 looks good to me
> C
[
https://issues.apache.org/jira/browse/HADOOP-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624543#action_12624543
]
Lohit Vijayarenu commented on HADOOP-2676:
--
bq. +1 to Runping's
[
https://issues.apache.org/jira/browse/HADOOP-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624521#action_12624521
]
Lohit Vijayarenu commented on HADOOP-2676:
--
Runping, I guess you mi
[
https://issues.apache.org/jira/browse/HADOOP-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624269#action_12624269
]
Lohit Vijayarenu commented on HADOOP-3985:
--
Can you see if you had any Data
[
https://issues.apache.org/jira/browse/HADOOP-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624076#action_12624076
]
Lohit Vijayarenu commented on HADOOP-3981:
--
One simple approach coul
[
https://issues.apache.org/jira/browse/HADOOP-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624059#action_12624059
]
Lohit Vijayarenu commented on HADOOP-3980:
--
We saw a case where local disk
Components: dfs
Affects Versions: 0.19.0
Reporter: Lohit Vijayarenu
Fix For: 0.19.0
SecondaryNameNode should make sure it has downloaded complete edits/fsimage
files before starting merge.
--
This message is automatically generated by JIRA.
-
You can reply to this email to
[
https://issues.apache.org/jira/browse/HADOOP-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-3948:
-
Attachment: hadoop-core-trunk.patch
Initial testing, namenode starts and works with
[
https://issues.apache.org/jira/browse/HADOOP-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-3948:
-
Attachment: hadoop-core-trunk.patch
Another version (untested), which compares compares
[
https://issues.apache.org/jira/browse/HADOOP-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623748#action_12623748
]
Lohit Vijayarenu commented on HADOOP-3948:
--
_FSEditLog::processIOError
[
https://issues.apache.org/jira/browse/HADOOP-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu updated HADOOP-3948:
-
Attachment: hadoop-core-trunk.patch
Attached is an initial version (untested) of the
Environment: LINUX. Executing ant test-libhdfs -Dcompile.c++=yes
-Dlibhdfs=1 -Dtest.output=yes
Reporter: Lohit Vijayarenu
Fix For: 0.19.0
HADOOP-3095 changed getFileBlockLocations API and HADOOP-3664 removed old one.
libhdfs was missed. On trunk test-libhdfs fails, we need
I am trying to run test-patch on trunk, but it seems to complain that findbugs
is broken on trunk.
This is the command I am using, anything changed?
ant -Dpatch.file=/home/lohit/tmp/EditsLogStreams.patch
-Dfindbugs.home=$FINDBUGS_HOME -Dforrest.home=$FORREST_HOME
-Djava5.home=$JAVA5_HOME test
[
https://issues.apache.org/jira/browse/HADOOP-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622977#action_12622977
]
Lohit Vijayarenu commented on HADOOP-3905:
--
+1 this looks good to me.
>
Hello Kunsheng,
You should also change Reducer's Key,Value pair. Now mapper is emitting
Text,Text instead of Text, IntWritable. And if you reducer outputs Text,Text as
well, you should change
conf.setOutputValueClass(IntWritable.class);
as well.
Thanks,
Lohit
- Original Me
[
https://issues.apache.org/jira/browse/HADOOP-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622281#action_12622281
]
Lohit Vijayarenu commented on HADOOP-3948:
--
Running few experiments
: Lohit Vijayarenu
NameNode's _edits_ and _fsimage_ should be separated with an option of having
them in their own separate directories.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/HADOOP-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621079#action_12621079
]
Lohit Vijayarenu commented on HADOOP-2665:
--
Christian, Do you still see
[
https://issues.apache.org/jira/browse/HADOOP-3433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lohit Vijayarenu resolved HADOOP-3433.
--
Resolution: Duplicate
This was resolved as part of HADOOP-3720. Closing this as
[
https://issues.apache.org/jira/browse/HADOOP-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620731#action_12620731
]
Lohit Vijayarenu commented on HADOOP-3062:
--
For this
bq. and break them dow
1 - 100 of 723 matches
Mail list logo
