[
https://issues.apache.org/jira/browse/HDFS-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276608#comment-13276608
]
Vinay commented on HDFS-2914:
-
Hi all,
According to the current patch proposed, there is no
[
https://issues.apache.org/jira/browse/HDFS-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay reassigned HDFS-3436:
---
Assignee: Vinay
Append to file is failing when one of the datanode where the block present is
down.
[
https://issues.apache.org/jira/browse/HDFS-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3436:
Description:
Scenario:
=
1. Cluster with 4 DataNodes.
2. Written file to 3 DNs, DN1-DN2-DN3
3. Stopped
[
https://issues.apache.org/jira/browse/HDFS-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13277724#comment-13277724
]
Vinay commented on HDFS-3436:
-
Scenario is as follows:
-
1. Cluster is
[
https://issues.apache.org/jira/browse/HDFS-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13278613#comment-13278613
]
Vinay commented on HDFS-3436:
-
Thanks Nicholas, that works. I will upload a patch for that.
[
https://issues.apache.org/jira/browse/HDFS-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HDFS-3436 started by Vinay.
Append to file is failing when one of the datanode where the block present is
down.
[
https://issues.apache.org/jira/browse/HDFS-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3436:
Fix Version/s: 2.0.1
Hadoop Flags: Reviewed
Status: Patch Available (was: In Progress)
adding
[
https://issues.apache.org/jira/browse/HDFS-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-2914:
Attachment: HDFS-2914.patch
Attaching patch for movement of NNRM from CommonService to ActiveService
[
https://issues.apache.org/jira/browse/HDFS-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3436:
Attachment: HDFS-3436.patch
Attaching the Patch for same
adding new datanode to existing
[
https://issues.apache.org/jira/browse/HDFS-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-2914:
Attachment: HDFS-2914-2.0.1.patch
HA: Standby should not enter safemode when resources are low
[
https://issues.apache.org/jira/browse/HDFS-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-2914:
Attachment: (was: HDFS-2914.patch)
HA: Standby should not enter safemode when resources are low
[
https://issues.apache.org/jira/browse/HDFS-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-2914:
Fix Version/s: 2.0.1
Target Version/s: 0.24.0, 2.0.1 (was: 0.24.0)
Affects Version/s: 2.0.1
[
https://issues.apache.org/jira/browse/HDFS-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13281177#comment-13281177
]
Vinay commented on HDFS-3436:
-
Hi Nicholas, I am working on it. Thanks.
[
https://issues.apache.org/jira/browse/HDFS-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-2914:
Attachment: (was: HDFS-2914-2.0.1.patch)
HA: Standby should not enter safemode when resources are low
[
https://issues.apache.org/jira/browse/HDFS-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-2914:
Status: Open (was: Patch Available)
Cancelling the recent patc on 2.0.1 branch
HA: Standby
[
https://issues.apache.org/jira/browse/HDFS-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-2914:
Attachment: HDFS-2914-trunk.patch
Attaching the Latest patch for trunk(3.0)
HA: Standby should
[
https://issues.apache.org/jira/browse/HDFS-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-2914:
Fix Version/s: (was: 2.0.1)
3.0.0
Target Version/s: 0.24.0, 2.0.1, 3.0.0 (was:
[
https://issues.apache.org/jira/browse/HDFS-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3436:
Status: Open (was: Patch Available)
adding new datanode to existing pipeline fails in case of
[
https://issues.apache.org/jira/browse/HDFS-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3436:
Attachment: HDFS-3436-trunk.patch
adding new datanode to existing pipeline fails in case of Append/Recovery
[
https://issues.apache.org/jira/browse/HDFS-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3436:
Fix Version/s: (was: 2.0.1)
3.0.0
Affects Version/s: 3.0.0
Status:
[
https://issues.apache.org/jira/browse/HDFS-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13281785#comment-13281785
]
Vinay commented on HDFS-3436:
-
Thanks a lot Nicholas.
adding new datanode to
Vinay created HDFS-3469:
---
Summary: start-dfs.sh will start zkfc, but stop-dfs.sh will not
stop zkfc similarly.
Key: HDFS-3469
URL: https://issues.apache.org/jira/browse/HDFS-3469
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3469:
Attachment: HDFS-3469.patch
Attached the Patch. Not adding any tests since this is only script change.
[
https://issues.apache.org/jira/browse/HDFS-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HDFS-3469 started by Vinay.
start-dfs.sh will start zkfc, but stop-dfs.sh will not stop zkfc similarly.
[
https://issues.apache.org/jira/browse/HDFS-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HDFS-3469 stopped by Vinay.
start-dfs.sh will start zkfc, but stop-dfs.sh will not stop zkfc similarly.
[
https://issues.apache.org/jira/browse/HDFS-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3469:
Fix Version/s: 3.0.0
Status: Patch Available (was: Open)
start-dfs.sh will start zkfc, but
[
https://issues.apache.org/jira/browse/HDFS-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay reassigned HDFS-3480:
---
Assignee: Vinay
Multiple SLF4J binding warning
--
Key:
[
https://issues.apache.org/jira/browse/HDFS-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13287220#comment-13287220
]
Vinay commented on HDFS-3480:
-
This is introduced after committing the HDFS-3042. zookeeper.jar
[
https://issues.apache.org/jira/browse/HDFS-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3480:
Attachment: HDFS-3480.patch
Multiple SLF4J binding warning
--
[
https://issues.apache.org/jira/browse/HDFS-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13287522#comment-13287522
]
Vinay commented on HDFS-3480:
-
Changed the scope of zookeeper.jar and slf4j-log4j12.jar to
[
https://issues.apache.org/jira/browse/HDFS-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3480:
Status: Patch Available (was: Open)
Multiple SLF4J binding warning
--
Vinay created HDFS-3507:
---
Summary: DFS#isInSafeNode needs to execute only on Active NameNode
Key: HDFS-3507
URL: https://issues.apache.org/jira/browse/HDFS-3507
Project: Hadoop HDFS
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HDFS-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13289947#comment-13289947
]
Vinay commented on HDFS-3507:
-
Adding to above description...
Since standby will not do any
[
https://issues.apache.org/jira/browse/HDFS-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3507:
Summary: DFS#isInSafeMode needs to execute only on Active NameNode (was:
DFS#isInSafeNode needs to execute only on
[
https://issues.apache.org/jira/browse/HDFS-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay reassigned HDFS-3507:
---
Assignee: Vinay
DFS#isInSafeMode needs to execute only on Active NameNode
[
https://issues.apache.org/jira/browse/HDFS-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13291642#comment-13291642
]
Vinay commented on HDFS-2914:
-
Thanks Aaron for the review and commit.
HA:
[
https://issues.apache.org/jira/browse/HDFS-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13293354#comment-13293354
]
Vinay commented on HDFS-3507:
-
Hi Nicholas,
{quote}For option 1, we may simply add a parameter
[
https://issues.apache.org/jira/browse/HDFS-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13293663#comment-13293663
]
Vinay commented on HDFS-3526:
-
Hi Brahma,
Thanks for filing this.
There is one more place
[
https://issues.apache.org/jira/browse/HDFS-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3507:
Target Version/s: 2.0.1-alpha, 3.0.0
Status: Patch Available (was: Open)
DFS#isInSafeMode needs
[
https://issues.apache.org/jira/browse/HDFS-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3507:
Attachment: HDFS-3507.patch
Attaching the patch with changes as suggested by nicholas
[
https://issues.apache.org/jira/browse/HDFS-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay reassigned HDFS-3541:
---
Assignee: Vinay
Deadlock between recovery, xceiver and packet responder
[
https://issues.apache.org/jira/browse/HDFS-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13395862#comment-13395862
]
Vinay commented on HDFS-3541:
-
By seeing the ThreadDump attached, recoverBlock(..) call is
[
https://issues.apache.org/jira/browse/HDFS-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3526:
Attachment: HDFS-3526.patch
Attaching the patch with above mentioned changes
Standy NameNode is
[
https://issues.apache.org/jira/browse/HDFS-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3526:
Affects Version/s: 3.0.0
Status: Patch Available (was: Open)
Standy NameNode is entering into
[
https://issues.apache.org/jira/browse/HDFS-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13396494#comment-13396494
]
Vinay commented on HDFS-1490:
-
Hi Molkov,
We also faced same problem in 2.0.1.
Are you
[
https://issues.apache.org/jira/browse/HDFS-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13396712#comment-13396712
]
Vinay commented on HDFS-3526:
-
{noformat}-1 javadoc. The javadoc tool appears to have generated
[
https://issues.apache.org/jira/browse/HDFS-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13397263#comment-13397263
]
Vinay commented on HDFS-3541:
-
Hi Lee,
I agree your suggestion.
But as of now there is no
[
https://issues.apache.org/jira/browse/HDFS-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13397265#comment-13397265
]
Vinay commented on HDFS-3541:
-
{quote}But as of now there is no way to stop the
Vinay created HDFS-3547:
---
Summary: Handle disconnect and session timeout events at BKJM
Key: HDFS-3547
URL: https://issues.apache.org/jira/browse/HDFS-3547
Project: Hadoop HDFS
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HDFS-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3547:
Description:
# Retry zookeeper operations for some amount of time in case of
CONNECTIONLOSS/OPERATIONTIMEOUT
[
https://issues.apache.org/jira/browse/HDFS-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13398427#comment-13398427
]
Vinay commented on HDFS-3541:
-
I found out the Actual Problem.
Problem resides in
[
https://issues.apache.org/jira/browse/HDFS-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3541:
Attachment: HDFS-3541.patch
Attaching the patch. Fixed as per suggestions by Lee. Please review..
[
https://issues.apache.org/jira/browse/HDFS-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3541:
Target Version/s: 0.23.3, 2.0.1-alpha, 3.0.0 (was: 0.23.3)
Status: Patch Available (was: Open)
[
https://issues.apache.org/jira/browse/HDFS-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3507:
Status: Open (was: Patch Available)
DFS#isInSafeMode needs to execute only on Active NameNode
[
https://issues.apache.org/jira/browse/HDFS-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3507:
Status: Patch Available (was: Open)
Submitting patch again, so that Hadoop QA can catch.
[
https://issues.apache.org/jira/browse/HDFS-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13399951#comment-13399951
]
Vinay commented on HDFS-3541:
-
Below failures are not replated to current patch
{noformat}-1
[
https://issues.apache.org/jira/browse/HDFS-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13400487#comment-13400487
]
Vinay commented on HDFS-3561:
-
During transition, fencing of old active will be done.
Here
[
https://issues.apache.org/jira/browse/HDFS-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13401163#comment-13401163
]
Vinay commented on HDFS-3507:
-
Thanks Aaron., I really did not know about it..
[
https://issues.apache.org/jira/browse/HDFS-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13402978#comment-13402978
]
Vinay commented on HDFS-3561:
-
{quote}This isn't acceptable. The point of fencing is to ensure
[
https://issues.apache.org/jira/browse/HDFS-3541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3541:
Attachment: HDFS-3541-2.patch
Attaching the patch which address above comments.
Thanks Lee for the hint to write
[
https://issues.apache.org/jira/browse/HDFS-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3561:
Attachment: HDFS-3561.patch
Attaching patch to reduce the number of retries for graceful fence
[
https://issues.apache.org/jira/browse/HDFS-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3561:
Affects Version/s: 3.0.0
2.0.1-alpha
Status: Patch Available (was: Open)
[
https://issues.apache.org/jira/browse/HDFS-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13410090#comment-13410090
]
Vinay commented on HDFS-3605:
-
{quote}The design of the code should be such that, it will
[
https://issues.apache.org/jira/browse/HDFS-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13410091#comment-13410091
]
Vinay commented on HDFS-3605:
-
@Uma
{quote}Here I have one question, why we are keeping all the
[
https://issues.apache.org/jira/browse/HDFS-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13410218#comment-13410218
]
Vinay commented on HDFS-3561:
-
Thanks Aaron for the suggestion.
I have one question here.
[
https://issues.apache.org/jira/browse/HDFS-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3562:
Attachment: HDFS-3562.patch
Attaching the patch
Handle disconnect and session timeout events at
[
https://issues.apache.org/jira/browse/HDFS-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3561:
Attachment: HDFS-3561-2.patch
Attaching the patch by addressing above comments
ZKFC retries for
[
https://issues.apache.org/jira/browse/HDFS-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13414316#comment-13414316
]
Vinay commented on HDFS-3561:
-
That sounds good. But as of now, in ZKFC, tryGracefulFence() is
[
https://issues.apache.org/jira/browse/HDFS-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3526:
Resolution: Not A Problem
Status: Resolved (was: Patch Available)
Resolving as Not a Problem as per
Vinay created HDFS-3734:
---
Summary: TestFSEditLogLoader.testReplicationAdjusted() will hang
if number of blocks are more than one
Key: HDFS-3734
URL: https://issues.apache.org/jira/browse/HDFS-3734
Project:
[
https://issues.apache.org/jira/browse/HDFS-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13426535#comment-13426535
]
Vinay commented on HDFS-3734:
-
I agree. Existing testcase will pass.
If we add one more file
[
https://issues.apache.org/jira/browse/HDFS-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13426537#comment-13426537
]
Vinay commented on HDFS-3734:
-
Here is the modified test case
{code}@Test(timeout = 6)
[
https://issues.apache.org/jira/browse/HDFS-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427101#comment-13427101
]
Vinay commented on HDFS-3734:
-
@Raju,
You are right. If that is fixed properly, then this test
Vinay created HDFS-3752:
---
Summary: BOOTSTRAPSTANDBY for new Standby node will not work just
after saveNameSpace at ANN in case of BKJM
Key: HDFS-3752
URL: https://issues.apache.org/jira/browse/HDFS-3752
[
https://issues.apache.org/jira/browse/HDFS-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13428582#comment-13428582
]
Vinay commented on HDFS-3734:
-
{quote}Because of the replication before the cluster restart is
Vinay created HDFS-3765:
---
Summary: Namenode INITIALIZESHAREDEDITS should be able to
initialize all shared storages
Key: HDFS-3765
URL: https://issues.apache.org/jira/browse/HDFS-3765
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3765:
Attachment: HDFS-3765.patch
Attached the patch for the same.
Namenode INITIALIZESHAREDEDITS
[
https://issues.apache.org/jira/browse/HDFS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13429912#comment-13429912
]
Vinay commented on HDFS-3765:
-
Thanks a lot Todd for taking a look.
{quote} I'm not 100%
[
https://issues.apache.org/jira/browse/HDFS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3765:
Description:
Currently, NameNode INITIALIZESHAREDEDITS provides ability to copy the edits
files to file schema
[
https://issues.apache.org/jira/browse/HDFS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3765:
Attachment: HDFS-3765.patch
Attaching the patch with comments fixed.
Namenode
[
https://issues.apache.org/jira/browse/HDFS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3765:
Status: Patch Available (was: Open)
Namenode INITIALIZESHAREDEDITS should be able to initialize all shared
[
https://issues.apache.org/jira/browse/HDFS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13431617#comment-13431617
]
Vinay commented on HDFS-3765:
-
{quote}NameNode -initializeSharedEdits (the command is not
[
https://issues.apache.org/jira/browse/HDFS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3765:
Attachment: HDFS-3765.patch
Attaching the patch with fixed comments
Namenode
[
https://issues.apache.org/jira/browse/HDFS-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13432946#comment-13432946
]
Vinay commented on HDFS-3561:
-
Hi [~atm] any more comments you have on this..?
[
https://issues.apache.org/jira/browse/HDFS-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13435937#comment-13435937
]
Vinay commented on HDFS-3618:
-
* Regarding StreamPumper thread getting hanged:
I tried to
[
https://issues.apache.org/jira/browse/HDFS-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3507:
Attachment: HDFS-3507.patch
Attaching the latest re-based patch
DFS#isInSafeMode needs to execute
[
https://issues.apache.org/jira/browse/HDFS-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13438463#comment-13438463
]
Vinay commented on HDFS-3561:
-
Thanks Aaron,
I agree with your preference. I will post a new
[
https://issues.apache.org/jira/browse/HDFS-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13438539#comment-13438539
]
Vinay commented on HDFS-3507:
-
Thanks Aaron for your inputs.
{quote}The new parameter in the
[
https://issues.apache.org/jira/browse/HDFS-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3561:
Attachment: HDFS-3561-3.patch
Attaching the patch with latest comment fixes.
ZKFC retries for 45
[
https://issues.apache.org/jira/browse/HDFS-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13439750#comment-13439750
]
Vinay commented on HDFS-3561:
-
Yes Aaron,
We tested the described scenario after setting number
[
https://issues.apache.org/jira/browse/HDFS-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442280#comment-13442280
]
Vinay commented on HDFS-3854:
-
Hi Uma, Thanks for posting this Jira.
Its really a good idea to
[
https://issues.apache.org/jira/browse/HDFS-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442325#comment-13442325
]
Vinay commented on HDFS-3809:
-
Hi Ivan,
Patch looks nice. Following are the simple comments
[
https://issues.apache.org/jira/browse/HDFS-3810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442343#comment-13442343
]
Vinay commented on HDFS-3810:
-
Hi Ivan,
Patch looks good.
Along with Rakesh's comment, one
[
https://issues.apache.org/jira/browse/HDFS-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442945#comment-13442945
]
Vinay commented on HDFS-3857:
-
Hi Todd,
This is same as HDFS-1490,
Patch is attached to
[
https://issues.apache.org/jira/browse/HDFS-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-1490:
Attachment: HDFS-1490.patch
Attaching the patch
TransferFSImage should timeout
[
https://issues.apache.org/jira/browse/HDFS-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay resolved HDFS-3857.
-
Resolution: Duplicate
Duplicate of HDFS-1490
Image transfer never times out on client isde
[
https://issues.apache.org/jira/browse/HDFS-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-3857:
Summary: Image transfer never times out on client side (was: Image
transfer never times out on client isde)
[
https://issues.apache.org/jira/browse/HDFS-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinay updated HDFS-1490:
Attachment: HDFS-1490.patch
Attaching the latest patch
TransferFSImage should timeout
[
https://issues.apache.org/jira/browse/HDFS-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443051#comment-13443051
]
Vinay commented on HDFS-1490:
-
{code} Call to equals() comparing different types in
[
https://issues.apache.org/jira/browse/HDFS-1490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13443791#comment-13443791
]
Vinay commented on HDFS-1490:
-
{quote}Why not introduce a new config which defaults to
1 - 100 of 574 matches
Mail list logo
