[
https://issues.apache.org/jira/browse/HDFS-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reassigned HDFS-2263:
-
Assignee: (was: Harsh J)
> Make DFSClient report bad blocks more quickly
>
[
https://issues.apache.org/jira/browse/HDFS-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reassigned HDFS-2561:
-
Assignee: (was: Harsh J)
> Under dfsadmin -report, show a proper 'last contact time' for
>
[
https://issues.apache.org/jira/browse/HDFS-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reassigned HDFS-1590:
-
Assignee: (was: Harsh J)
> Decommissioning never ends when node to decommission has blocks that are
[
https://issues.apache.org/jira/browse/HDFS-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reassigned HDFS-4638:
-
Assignee: (was: Harsh J)
> TransferFsImage should take Configuration as parameter
>
[
https://issues.apache.org/jira/browse/HDFS-8516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reassigned HDFS-8516:
-
Assignee: (was: Harsh J)
> The 'hdfs crypto -listZones' should not print an extra newline at end of
[
https://issues.apache.org/jira/browse/HDFS-10237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reassigned HDFS-10237:
--
Assignee: (was: Harsh J)
> Support specifying checksum type in WebHDFS/HTTPFS writers
>
[
https://issues.apache.org/jira/browse/HDFS-11421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16025565#comment-16025565
]
Harsh J commented on HDFS-11421:
The patch looks good to me. Were the style changes done out of checkstyle
[
https://issues.apache.org/jira/browse/HDFS-9868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907295#comment-15907295
]
Harsh J commented on HDFS-9868:
---
Would this mapping allow DistCp to be aware of destination's distinct KMS
[
https://issues.apache.org/jira/browse/HDFS-7290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15901175#comment-15901175
]
Harsh J commented on HDFS-7290:
---
[~ajisakaa] or [~jojochuang], could you help review this simple exception
[
https://issues.apache.org/jira/browse/HDFS-11421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15891804#comment-15891804
]
Harsh J commented on HDFS-11421:
[~xiaochen] - Thanks! I'm uncertain how to trigger just a branch-2 build,
[
https://issues.apache.org/jira/browse/HDFS-11421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-11421:
---
Target Version/s: 2.9.0, 3.0.0-beta1 (was: 2.9.0)
> Make WebHDFS' ACLs RegEx configurable
>
[
https://issues.apache.org/jira/browse/HDFS-11421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-11421:
---
Attachment: HDFS-11421.000.patch
HDFS-11421-branch-2.000.patch
Thank you for the review
[
https://issues.apache.org/jira/browse/HDFS-11422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871117#comment-15871117
]
Harsh J commented on HDFS-11422:
IIRC, you can also use the command {{hdfs dfsadmin
[
https://issues.apache.org/jira/browse/HDFS-11422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871115#comment-15871115
]
Harsh J commented on HDFS-11422:
Does the feature offered by {{dfs.namenode.name.dir.restore}} help, even
[
https://issues.apache.org/jira/browse/HDFS-11421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-11421:
---
Affects Version/s: 2.6.0
Target Version/s: 2.9.0
Status: Patch Available (was: Open)
>
Harsh J created HDFS-11421:
--
Summary: Make WebHDFS' ACLs RegEx configurable
Key: HDFS-11421
URL: https://issues.apache.org/jira/browse/HDFS-11421
Project: Hadoop HDFS
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/HDFS-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-3302:
--
Assignee: (was: Harsh J)
> Review and improve HDFS trash documentation
>
[
https://issues.apache.org/jira/browse/HDFS-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15825810#comment-15825810
]
Harsh J commented on HDFS-3302:
---
Just a short note: This seems to be incorrectly attributed (to me). Actual
[
https://issues.apache.org/jira/browse/HDFS-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-2569.
---
Resolution: Cannot Reproduce
Assignee: (was: Harsh J)
Cannot quite reproduce this on current
[
https://issues.apache.org/jira/browse/HDFS-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-2936:
--
Description:
If an admin wishes to enforce replication today for all the users of their
cluster, they may set
[
https://issues.apache.org/jira/browse/HDFS-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-2936:
--
Summary: Provide a way to apply a minimum replication factor aside of
strict minimum live replicas feature
[
https://issues.apache.org/jira/browse/HDFS-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-2936:
--
Assignee: (was: Harsh J)
> Provide a way to apply a minimum replication factor aside of strict minimum
>
[
https://issues.apache.org/jira/browse/HDFS-11012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-11012:
---
Status: Patch Available (was: Open)
> Unnecessary INFO logging on DFSClients for InvalidToken
>
Harsh J created HDFS-11012:
--
Summary: Unnecessary INFO logging on DFSClients for InvalidToken
Key: HDFS-11012
URL: https://issues.apache.org/jira/browse/HDFS-11012
Project: Hadoop HDFS
Issue Type:
[
https://issues.apache.org/jira/browse/HDFS-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15312138#comment-15312138
]
Harsh J commented on HDFS-3584:
---
HDFS-10240 appears to report a similar issue.
> Blocks are getting marked
[
https://issues.apache.org/jira/browse/HDFS-10240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15295930#comment-15295930
]
Harsh J commented on HDFS-10240:
This seems similar to the situation described in HDFS-3584. The comment
[
https://issues.apache.org/jira/browse/HDFS-3557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-3557.
---
Resolution: Not A Problem
Resolving per comment (also stale)
> provide means of escaping special characters
[
https://issues.apache.org/jira/browse/HDFS-10296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15251966#comment-15251966
]
Harsh J commented on HDFS-10296:
We do special handling in DistributedFileSystem#addDelegationTokens to
[
https://issues.apache.org/jira/browse/HDFS-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15243980#comment-15243980
]
Harsh J edited comment on HDFS-8161 at 4/16/16 3:26 AM:
[~brahmareddy] - was this
[
https://issues.apache.org/jira/browse/HDFS-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15243980#comment-15243980
]
Harsh J commented on HDFS-8161:
---
[~brahmareddy] - was this encountered on virtual machine hosts, or physical
[
https://issues.apache.org/jira/browse/HDFS-10237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-10237:
---
Attachment: HDFS-10237.002.patch
> Support specifying checksum type in WebHDFS/HTTPFS writers
>
[
https://issues.apache.org/jira/browse/HDFS-10237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-10237:
---
Status: Open (was: Patch Available)
> Support specifying checksum type in WebHDFS/HTTPFS writers
>
[
https://issues.apache.org/jira/browse/HDFS-10237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-10237:
---
Status: Patch Available (was: Open)
> Support specifying checksum type in WebHDFS/HTTPFS writers
>
[
https://issues.apache.org/jira/browse/HDFS-10237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-10237:
---
Attachment: HDFS-10237.002.patch
Addressed most checkstyle issues except the ones about the warnings
[
https://issues.apache.org/jira/browse/HDFS-10237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-10237:
---
Attachment: HDFS-10237.001.patch
* Fixed the javadoc extra param problem
* Fixed logic in the
[
https://issues.apache.org/jira/browse/HDFS-6542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-6542.
---
Resolution: Duplicate
I missed this JIRA when searching before I filed HDFS-10237, but now noticed
via
[
https://issues.apache.org/jira/browse/HDFS-10237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-10237:
---
Attachment: HDFS-10237.000.patch
> Support specifying checksum type in WebHDFS/HTTPFS writers
>
[
https://issues.apache.org/jira/browse/HDFS-10237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-10237:
---
Status: Patch Available (was: Open)
> Support specifying checksum type in WebHDFS/HTTPFS writers
>
Harsh J created HDFS-10237:
--
Summary: Support specifying checksum type in WebHDFS/HTTPFS writers
Key: HDFS-10237
URL: https://issues.apache.org/jira/browse/HDFS-10237
Project: Hadoop HDFS
Issue
[
https://issues.apache.org/jira/browse/HDFS-10221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15215876#comment-15215876
]
Harsh J commented on HDFS-10221:
It appears we can also request the parser to allow comments as a feature,
[
https://issues.apache.org/jira/browse/HDFS-9949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-9949:
--
Description:
In the following scenario, in releases without HDFS-8211, the DN may regenerate
its UUIDs
[
https://issues.apache.org/jira/browse/HDFS-9949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-9949:
--
Attachment: HDFS-9949.001.patch
Thank you for reviewing [~cmccabe]! Agreed, I should've used a smaller sleep.
[
https://issues.apache.org/jira/browse/HDFS-9949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-9949:
--
Description:
In the following scenario, in releases without HDFS-8211, the DN may regenerate
its UUIDs
[
https://issues.apache.org/jira/browse/HDFS-9940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15192340#comment-15192340
]
Harsh J commented on HDFS-9940:
---
Agreed on the confusion when there's role-based config management involved -
[
https://issues.apache.org/jira/browse/HDFS-9949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15192335#comment-15192335
]
Harsh J commented on HDFS-9949:
---
bq. -1 unit *
Patch only adds a test-case; the failing tests appear flaky
[
https://issues.apache.org/jira/browse/HDFS-9949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-9949:
--
Target Version/s: 3.0.0, 2.8.0, 2.9.0
Status: Patch Available (was: Open)
> Testcase for catching
[
https://issues.apache.org/jira/browse/HDFS-9949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-9949:
--
Attachment: (was: HDFS-9949.000.patch)
> Testcase for catching DN UUID regeneration regression
>
[
https://issues.apache.org/jira/browse/HDFS-9949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-9949:
--
Attachment: HDFS-9949.000.patch
> Testcase for catching DN UUID regeneration regression
>
[
https://issues.apache.org/jira/browse/HDFS-9949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-9949:
--
Attachment: HDFS-9949.000.branch-2.7.not-for-commit.patch
HDFS-9949.000.patch
> Testcase for
Harsh J created HDFS-9949:
-
Summary: Testcase for catching DN UUID regeneration regression
Key: HDFS-9949
URL: https://issues.apache.org/jira/browse/HDFS-9949
Project: Hadoop HDFS
Issue Type: Test
[
https://issues.apache.org/jira/browse/HDFS-8475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-8475.
---
Resolution: Not A Bug
I don't see a bug reported here - the report says the write was done with a
single
[
https://issues.apache.org/jira/browse/HDFS-9521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-9521:
--
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.9.0
Status: Resolved (was:
[
https://issues.apache.org/jira/browse/HDFS-9521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15182915#comment-15182915
]
Harsh J commented on HDFS-9521:
---
+1.
The check-point related tests in one of the tests seemed relevant but
[
https://issues.apache.org/jira/browse/HDFS-9521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-9521:
--
Attachment: HDFS-9521.004.patch
LGTM. Just had two checkstyle nits I've corrected in this variant, aside of
[
https://issues.apache.org/jira/browse/HDFS-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15171424#comment-15171424
]
Harsh J commented on HDFS-4936:
---
Forgot to add the response of the asker:
{quote}
After 200 million years,
[
https://issues.apache.org/jira/browse/HDFS-9868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15171119#comment-15171119
]
Harsh J commented on HDFS-9868:
---
Does the feature added with HDFS-6376 not suffice?
> add reading source
[
https://issues.apache.org/jira/browse/HDFS-8509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-8509:
--
Issue Type: Improvement (was: Task)
> Support different passwords for key and keystore on HTTPFS using SSL.
[
https://issues.apache.org/jira/browse/HDFS-9521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082446#comment-15082446
]
Harsh J commented on HDFS-9521:
---
Patch's approach looks good to me. Agreed with [~liuml07], that we can keep
[
https://issues.apache.org/jira/browse/HDFS-7447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15054098#comment-15054098
]
Harsh J commented on HDFS-7447:
---
bq. The number of entries in a single ACL is capped at a maximum of 32.
[
https://issues.apache.org/jira/browse/HDFS-8298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15006787#comment-15006787
]
Harsh J commented on HDFS-8298:
---
I'm closing this JIRA as Invalid. This is not a bug, but a misunderstanding
[
https://issues.apache.org/jira/browse/HDFS-8298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-8298.
---
Resolution: Invalid
Closing out - for specific identified improvements (such as log improvements,
or ideas
[
https://issues.apache.org/jira/browse/HDFS-8298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-8298:
--
Environment: (was: HDP 2.2)
> HA: NameNode should not shut down completely without quorum, doesn't recover
[
https://issues.apache.org/jira/browse/HDFS-8986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14994469#comment-14994469
]
Harsh J commented on HDFS-8986:
---
This continues to cause a bunch of confusion among our user-base who are
[
https://issues.apache.org/jira/browse/HDFS-8986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14984274#comment-14984274
]
Harsh J commented on HDFS-8986:
---
[~jagadesh.kiran] - What's the precise opposition w.r.t. adding a new flag
[
https://issues.apache.org/jira/browse/HDFS-9257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14960854#comment-14960854
]
Harsh J commented on HDFS-9257:
---
+1, failed tests are unrelated. Tests shouldn't be necessary for the trivial
[
https://issues.apache.org/jira/browse/HDFS-9257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-9257:
--
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.8.0
Status: Resolved (was:
[
https://issues.apache.org/jira/browse/HDFS-7899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14945253#comment-14945253
]
Harsh J commented on HDFS-7899:
---
Thank you [~jagadesh.kiran] and [~vinayrpet]
> Improve EOF error message
>
[
https://issues.apache.org/jira/browse/HDFS-7899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14942281#comment-14942281
]
Harsh J commented on HDFS-7899:
---
Sorry on delay here!
Perhaps it could be fixed to:
s/Unexpected EOF while
[
https://issues.apache.org/jira/browse/HDFS-6674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-6674.
---
Resolution: Invalid
The hang, if still valid, seems to result as an outcome of the underlying Java
libraries
[
https://issues.apache.org/jira/browse/HDFS-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-4224.
---
Resolution: Invalid
Invalid after HDFS-7430
> The dncp_block_verification log can be compressed
>
[
https://issues.apache.org/jira/browse/HDFS-7899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14733250#comment-14733250
]
Harsh J commented on HDFS-7899:
---
Thanks Jagadesh, that message change was just a small idea to make it carry
[
https://issues.apache.org/jira/browse/HDFS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-237.
--
Resolution: Later
This older JIRA is a bit stale given the multiple changes that went into the
RPC side. Follow
[
https://issues.apache.org/jira/browse/HDFS-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-2390:
--
Issue Type: Improvement (was: Bug)
dfsadmin -setBalancerBandwidth doesnot validate -ve value
[
https://issues.apache.org/jira/browse/HDFS-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14716463#comment-14716463
]
Harsh J commented on HDFS-2390:
---
+1 on v4. The check style warning is about file length, but
[
https://issues.apache.org/jira/browse/HDFS-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-2390:
--
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.8.0
Status: Resolved (was:
[
https://issues.apache.org/jira/browse/HDFS-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-2390:
--
Priority: Minor (was: Major)
dfsadmin -setBalancerBandwidth doesnot validate -ve value
[
https://issues.apache.org/jira/browse/HDFS-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14714205#comment-14714205
]
Harsh J commented on HDFS-2390:
---
bq. +assertEquals(Bandwidth should be a non-negative
[
https://issues.apache.org/jira/browse/HDFS-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1479#comment-1479
]
Harsh J commented on HDFS-5696:
---
Thanks for reporting this. Care to submit a fix changing the
[
https://issues.apache.org/jira/browse/HDFS-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-8118:
--
Hadoop Flags: Reviewed
Affects Version/s: 2.7.1
Target Version/s: 3.0.0, 2.8.0
[
https://issues.apache.org/jira/browse/HDFS-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14709034#comment-14709034
]
Harsh J commented on HDFS-8118:
---
I missed a small detail - why is the {{new Date()}} not
[
https://issues.apache.org/jira/browse/HDFS-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-8118:
--
Comment: was deleted
(was: I missed a small detail - why is the {{new Date()}} not outside the
user-directory
[
https://issues.apache.org/jira/browse/HDFS-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14710624#comment-14710624
]
Harsh J commented on HDFS-8118:
---
Thanks Casey,
You can run individual tests locally via
[
https://issues.apache.org/jira/browse/HDFS-8821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-8821:
--
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 2.8.0
Status: Resolved (was:
[
https://issues.apache.org/jira/browse/HDFS-8821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641777#comment-14641777
]
Harsh J commented on HDFS-8821:
---
+1 looks good to me. This should help avoid the continual
[
https://issues.apache.org/jira/browse/HDFS-8486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-8486:
--
Release Note:
Public service notice:
- Every restart of a 2.6.x or 2.7.0 DN incurs a risk of unwanted block
[
https://issues.apache.org/jira/browse/HDFS-8660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14613063#comment-14613063
]
Harsh J commented on HDFS-8660:
---
This would be an excellent improvement for certain
[
https://issues.apache.org/jira/browse/HDFS-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14572631#comment-14572631
]
Harsh J commented on HDFS-3627:
---
bq. Its used only for the old Pre-protobuf images.
Yup but
[
https://issues.apache.org/jira/browse/HDFS-8516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14570433#comment-14570433
]
Harsh J commented on HDFS-8516:
---
I wasn't worried of the usage ones as I'd never parse them
Harsh J created HDFS-8516:
-
Summary: The 'hdfs crypto -listZones' should not print an extra
newline at end of output
Key: HDFS-8516
URL: https://issues.apache.org/jira/browse/HDFS-8516
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-8516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-8516:
--
Attachment: HDFS-8516.patch
The 'hdfs crypto -listZones' should not print an extra newline at end of
output
[
https://issues.apache.org/jira/browse/HDFS-8516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-8516:
--
Target Version/s: 2.8.0
Affects Version/s: 2.7.0
Status: Patch Available (was: Open)
The
[
https://issues.apache.org/jira/browse/HDFS-7097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-7097:
--
Target Version/s: (was: 2.6.0)
Allow block reports to be processed during checkpointing on standby name node
[
https://issues.apache.org/jira/browse/HDFS-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-7442:
--
Affects Version/s: 2.6.0
Optimization for decommission-in-progress check
[
https://issues.apache.org/jira/browse/HDFS-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-7442:
--
Component/s: namenode
Optimization for decommission-in-progress check
[
https://issues.apache.org/jira/browse/HDFS-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HDFS-3493:
--
Component/s: namenode
Invalidate excess corrupted blocks as long as minimum replication is satisfied
[
https://issues.apache.org/jira/browse/HDFS-7960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reassigned HDFS-7960:
-
Assignee: Colin Patrick McCabe (was: Samuel Otero Schmidt)
The full block report should prune zombie
[
https://issues.apache.org/jira/browse/HDFS-8118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14505791#comment-14505791
]
Harsh J commented on HDFS-8118:
---
Thanks for explaining that Casey. It makes sense to
[
https://issues.apache.org/jira/browse/HDFS-8113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14496446#comment-14496446
]
Harsh J commented on HDFS-8113:
---
Stale block copies leftover in the DN can cause the
[
https://issues.apache.org/jira/browse/HDFS-7452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14484575#comment-14484575
]
Harsh J commented on HDFS-7452:
---
IIUC, the Web UI of SBN tries to load up corrupt/missing
[
https://issues.apache.org/jira/browse/HDFS-7306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-7306.
---
Resolution: Duplicate
This should be resolved via HDFS-5579.
can't decommission w/under construction blocks
1 - 100 of 645 matches
Mail list logo
