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-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
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-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
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-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-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-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
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-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
[
https://issues.apache.org/jira/browse/HDFS-3349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-3349.
---
Resolution: Cannot Reproduce
Target Version/s: (was: 2.0.0-alpha)
Trying with lack of credentials
[
https://issues.apache.org/jira/browse/HDFS-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-2360.
---
Resolution: Not a Problem
The last line of the command (excluding the log and its stack trace via the
WARN)
[
https://issues.apache.org/jira/browse/HDFS-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-5740.
---
Resolution: Not a Problem
This is no longer an issue on branch-2 and trunk today. The command accepts a
[
https://issues.apache.org/jira/browse/HDFS-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-4494.
---
Resolution: Done
Target Version/s: 2.1.0-beta, 3.0.0 (was: 3.0.0, 2.1.0-beta)
This seems resolved
[
https://issues.apache.org/jira/browse/HDFS-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-4290.
---
Resolution: Later
Specific problems/use-cases driving this need haven't been bought up in the
past years.
[
https://issues.apache.org/jira/browse/HDFS-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-3621.
---
Resolution: Won't Fix
Thanks for the work Plamen!
Add a main method to HdfsConfiguration, for debug purposes
Harsh J created HDFS-7899:
-
Summary: Improve EOF error message
Key: HDFS-7899
URL: https://issues.apache.org/jira/browse/HDFS-7899
Project: Hadoop HDFS
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/HDFS-5688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-5688.
---
Resolution: Cannot Reproduce
Wire-encription in QJM
--
Key: HDFS-5688
[
https://issues.apache.org/jira/browse/HDFS-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-7752.
---
Resolution: Fixed
Fix Version/s: 2.7.0
Target Version/s: (was: 2.7.0)
Thanks Wellington!
[
https://issues.apache.org/jira/browse/HDFS-7580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-7580.
---
Resolution: Invalid
Looking at the JDK sources there's no way to programmatically configure the KDC
timeouts,
[
https://issues.apache.org/jira/browse/HDFS-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-7532.
---
Resolution: Duplicate
Should be eventually fixed via HDFS-7430.
Yes, you may shutdown the affected DN
Harsh J created HDFS-7580:
-
Summary: NN - JN communication should use reusable authentication
methods
Key: HDFS-7580
URL: https://issues.apache.org/jira/browse/HDFS-7580
Project: Hadoop HDFS
Issue
Harsh J created HDFS-7546:
-
Summary: Document, and set an accepting default for
dfs.namenode.kerberos.principal.pattern
Key: HDFS-7546
URL: https://issues.apache.org/jira/browse/HDFS-7546
Project: Hadoop
Harsh J created HDFS-7501:
-
Summary: TransactionsSinceLastCheckpoint can be negative on SBNs
Key: HDFS-7501
URL: https://issues.apache.org/jira/browse/HDFS-7501
Project: Hadoop HDFS
Issue Type: Bug
Harsh J created HDFS-7290:
-
Summary: Add HTTP response code to the HttpPutFailedException
message
Key: HDFS-7290
URL: https://issues.apache.org/jira/browse/HDFS-7290
Project: Hadoop HDFS
Issue
[
https://issues.apache.org/jira/browse/HDFS-3534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-3534.
---
Resolution: Not A Problem
As explained in above comments, this is expected behaviour. Resolving.
[
https://issues.apache.org/jira/browse/HDFS-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-160.
--
Resolution: Cannot Reproduce
This has likely gone stale now, and no similar reports have been received (PPC
may
[
https://issues.apache.org/jira/browse/HDFS-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-114.
--
Resolution: Duplicate
Remove code related to OP_READ_METADATA from DataNode
[
https://issues.apache.org/jira/browse/HDFS-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-156.
--
Resolution: Duplicate
Fixed indirectly via HADOOP-4656's change set. The 'id' command is now used
instead of
[
https://issues.apache.org/jira/browse/HDFS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-184.
--
Resolution: Not A Problem
This doesn't appear to be a problem today, esp. after the new edits and fsimage
[
https://issues.apache.org/jira/browse/HDFS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-174.
--
Resolution: Not A Problem
HDFS currently has proper Windows environment support without relying on local
[
https://issues.apache.org/jira/browse/HDFS-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-285.
--
Resolution: Not A Problem
This has likely gone stale (probably addressed at a higher level via Raghu's
earliest
[
https://issues.apache.org/jira/browse/HDFS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-345.
--
Resolution: Implemented
This is pretty close to the HDFS HA mechanism available in current versions.
Resolving
[
https://issues.apache.org/jira/browse/HDFS-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-372.
--
Resolution: Not A Problem
The invalidation of blocks was deliberately moved onto using the async disk
deletion
[
https://issues.apache.org/jira/browse/HDFS-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-386.
--
Resolution: Duplicate
NameNode webUI should show the config it is running with.
[
https://issues.apache.org/jira/browse/HDFS-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-431.
--
Resolution: Invalid
This is now Invalid since we've moved on to using CMake as the build framework
instead.
[
https://issues.apache.org/jira/browse/HDFS-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-803.
--
Resolution: Not A Problem
Resolving as 'Not a Problem' (anymore) as we've long since moved onto using
Maven
[
https://issues.apache.org/jira/browse/HDFS-2892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-2892.
---
Resolution: Invalid
Target Version/s: (was: 2.0.0-alpha, 3.0.0)
Resolving as Invalid as these
[
https://issues.apache.org/jira/browse/HDFS-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-198.
--
Resolution: Not A Problem
This one has gone very stale and we have not seen any properly true reports of
lease
Harsh J created HDFS-5802:
-
Summary: NameNode does not check for inode type before traversing
down a path
Key: HDFS-5802
URL: https://issues.apache.org/jira/browse/HDFS-5802
Project: Hadoop HDFS
Harsh J created HDFS-5189:
-
Summary: Rename the CorruptBlocks metric to CorruptReplicas
Key: HDFS-5189
URL: https://issues.apache.org/jira/browse/HDFS-5189
Project: Hadoop HDFS
Issue Type:
[
https://issues.apache.org/jira/browse/HDFS-5046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-5046.
---
Resolution: Not A Problem
bq. a). decommission progress hangs and the status always be 'Waiting DataNode
[
https://issues.apache.org/jira/browse/HDFS-4991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-4991.
---
Resolution: Invalid
First off, please do not use the JIRA as a QA medium. The HDFS project
provides and
Harsh J created HDFS-4983:
-
Summary: Numeric usernames do not work with WebHDFS FS
Key: HDFS-4983
URL: https://issues.apache.org/jira/browse/HDFS-4983
Project: Hadoop HDFS
Issue Type: Improvement
Harsh J created HDFS-4936:
-
Summary: Handle overflow condition for txid going over
Long.MAX_VALUE
Key: HDFS-4936
URL: https://issues.apache.org/jira/browse/HDFS-4936
Project: Hadoop HDFS
Issue
[
https://issues.apache.org/jira/browse/HDFS-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-4936.
---
Resolution: Not A Problem
Handle overflow condition for txid going over Long.MAX_VALUE
[
https://issues.apache.org/jira/browse/HDFS-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-2316.
---
Resolution: Fixed
Target Version/s: (was: 0.22.1)
[umbrella] WebHDFS: a complete FileSystem
[
https://issues.apache.org/jira/browse/HDFS-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-4630.
---
Resolution: Invalid
Closing again per Suresh's comment, as this is by design and you're merely
required to
[
https://issues.apache.org/jira/browse/HDFS-4624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-4624.
---
Resolution: Invalid
eclipse plugin for hadoop 2.0.0-alpha
-
[
https://issues.apache.org/jira/browse/HDFS-4509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-4509.
---
Resolution: Duplicate
Dupe of HDFS-4420.
Provide a way to ask Balancer to exclude certain
Harsh J created HDFS-4508:
-
Summary: Two minor improvements to the QJM Deployment docs
Key: HDFS-4508
URL: https://issues.apache.org/jira/browse/HDFS-4508
Project: Hadoop HDFS
Issue Type: Bug
Harsh J created HDFS-4509:
-
Summary: Provide a way to ask Balancer to exclude certain
DataNodes in its computation and/or work.
Key: HDFS-4509
URL: https://issues.apache.org/jira/browse/HDFS-4509
Project:
[
https://issues.apache.org/jira/browse/HDFS-976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-976.
--
Resolution: Duplicate
A working HDFS HA mode has been implemented via HDFS-1623. Closing this one out
as a
Harsh J created HDFS-4449:
-
Summary: When a decommission is awaiting closure of live blocks,
show the block IDs on the NameNode's UI report
Key: HDFS-4449
URL: https://issues.apache.org/jira/browse/HDFS-4449
[
https://issues.apache.org/jira/browse/HDFS-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-3801.
---
Resolution: Won't Fix
Hi Suresh and others,
Yes I agree, we can close this. It is better to go with a
[
https://issues.apache.org/jira/browse/HDFS-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-4425.
---
Resolution: Invalid
The Apache JIRA is not for user help but only for confirmed bug reports. Please
send
Harsh J created HDFS-4255:
-
Summary: Useless stacktrace shown in DN when there's an error
writing a block
Key: HDFS-4255
URL: https://issues.apache.org/jira/browse/HDFS-4255
Project: Hadoop HDFS
Harsh J created HDFS-4259:
-
Summary: Improve pipeline DN replacement failure message
Key: HDFS-4259
URL: https://issues.apache.org/jira/browse/HDFS-4259
Project: Hadoop HDFS
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/HDFS-4069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-4069.
---
Resolution: Won't Fix
File mode bits of some scripts in rpm package are incorrect
Harsh J created HDFS-4002:
-
Summary: Tool-ize OfflineImageViewer and make sure it returns
proper return codes upon exit
Key: HDFS-4002
URL: https://issues.apache.org/jira/browse/HDFS-4002
Project: Hadoop
Harsh J created HDFS-3968:
-
Summary: TestPersistBlocks seems to fail intermittently
Key: HDFS-3968
URL: https://issues.apache.org/jira/browse/HDFS-3968
Project: Hadoop HDFS
Issue Type: Test
[
https://issues.apache.org/jira/browse/HDFS-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-2530.
---
Resolution: Invalid
Hi Xie,
Please post the patch along with the parent JIRA itself, to keep the commits
Harsh J created HDFS-3886:
-
Summary: Shutdown requests can possibly check for checkpoint
issues (corrupted edits) and save a good namespace copy before closing down?
Key: HDFS-3886
URL:
Harsh J created HDFS-3801:
-
Summary: Provide a way to disable browsing of the files from the
web UI
Key: HDFS-3801
URL: https://issues.apache.org/jira/browse/HDFS-3801
Project: Hadoop HDFS
Issue
[
https://issues.apache.org/jira/browse/HDFS-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-3647.
---
Resolution: Fixed
Fix Version/s: 1.2.0
Target Version/s: (was: 1.2.0)
Hadoop Flags:
Harsh J created HDFS-3628:
-
Summary: The dfsadmin -setBalancerBandwidth command does not check
for superuser privileges
Key: HDFS-3628
URL: https://issues.apache.org/jira/browse/HDFS-3628
Project: Hadoop
Harsh J created HDFS-3621:
-
Summary: Add a main method to HdfsConfiguration, for debug purposes
Key: HDFS-3621
URL: https://issues.apache.org/jira/browse/HDFS-3621
Project: Hadoop HDFS
Issue Type:
Harsh J created HDFS-3611:
-
Summary: NameNode prints unnecessary WARNs about edit log normally
skipping a few bytes
Key: HDFS-3611
URL: https://issues.apache.org/jira/browse/HDFS-3611
Project: Hadoop HDFS
Harsh J created HDFS-3612:
-
Summary: Single namenode image directory config warning can be
improved
Key: HDFS-3612
URL: https://issues.apache.org/jira/browse/HDFS-3612
Project: Hadoop HDFS
Issue
Harsh J created HDFS-3613:
-
Summary: GSet prints some INFO level values, which aren't really
very useful to all
Key: HDFS-3613
URL: https://issues.apache.org/jira/browse/HDFS-3613
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-1125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-1125.
---
Resolution: Duplicate
Resolved via HDFS-1773. It was in the version after the one Allen tried above I
think,
Harsh J created HDFS-3567:
-
Summary: Provide a way to enforce clearing of trash data
immediately
Key: HDFS-3567
URL: https://issues.apache.org/jira/browse/HDFS-3567
Project: Hadoop HDFS
Issue Type:
Harsh J created HDFS-3570:
-
Summary: Balancer shouldn't rely on DFS Space Used % as that
ignores non-DFS used space
Key: HDFS-3570
URL: https://issues.apache.org/jira/browse/HDFS-3570
Project: Hadoop HDFS
Harsh J created HDFS-3560:
-
Summary: Enable automatic NameNode name-directory restore by
default
Key: HDFS-3560
URL: https://issues.apache.org/jira/browse/HDFS-3560
Project: Hadoop HDFS
Issue Type:
[
https://issues.apache.org/jira/browse/HDFS-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reopened HDFS-3522:
---
Reopening issue until comments and test are both addressed, just to have it
noticed :)
If NN
[
https://issues.apache.org/jira/browse/HDFS-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-3522.
---
Resolution: Fixed
I am good with this change. Resolving. Thanks Nicholas for catching my blunder
:)
Harsh J created HDFS-3475:
-
Summary: Make the replication monitor multipliers configurable
Key: HDFS-3475
URL: https://issues.apache.org/jira/browse/HDFS-3475
Project: Hadoop HDFS
Issue Type:
Harsh J created HDFS-3476:
-
Summary: Correct the default used in
TestDFSClientRetries.busyTest() after HDFS-3462
Key: HDFS-3476
URL: https://issues.apache.org/jira/browse/HDFS-3476
Project: Hadoop HDFS
Harsh J created HDFS-3358:
-
Summary: Specify explicitly that the NN UI status total is talking
of persistent objects on heap.
Key: HDFS-3358
URL: https://issues.apache.org/jira/browse/HDFS-3358
Project:
Harsh J created HDFS-3366:
-
Summary: Some stacktraces are now too lengthy and sometimes no good
Key: HDFS-3366
URL: https://issues.apache.org/jira/browse/HDFS-3366
Project: Hadoop HDFS
Issue Type:
[
https://issues.apache.org/jira/browse/HDFS-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-3366.
---
Resolution: Invalid
Actually, never mind. The
DN should log a WARN, not an INFO when it detects a corruption during block
transfer
Key: HDFS-2349
URL: https://issues.apache.org/jira/browse/HDFS-2349
Project:
With just 1 block on the HDFS cluster, NN exits safemode on startup immediately.
Key: HDFS-2311
URL: https://issues.apache.org/jira/browse/HDFS-2311
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-112.
--
Resolution: Not A Problem
This JIRA has grown stale over years and needs to be closed. The tests
framework has
[
https://issues.apache.org/jira/browse/HDFS-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-70.
-
Resolution: Won't Fix
HADOOP-266 was resolved as a Won't Fix and the DN currently works OK with the
way it
[
https://issues.apache.org/jira/browse/HDFS-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-339.
--
Resolution: Not A Problem
The introduction of the DFS Balancer (post '06, apparently) provides the
feature of
[
https://issues.apache.org/jira/browse/HDFS-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-251.
--
Resolution: Duplicate
Duplicate of https://issues.apache.org/jira/browse/HDFS-782 (closing this one,
since the
[
https://issues.apache.org/jira/browse/HDFS-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-128.
--
Resolution: Not A Problem
This is more of a browser issue. For instance, Chrome chooses to replace the
[
https://issues.apache.org/jira/browse/HDFS-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-186.
--
Resolution: Not A Problem
I just loaded 2000 files to test this. The web browser loads the list just fine.
Even
Add tests for ensuring that the DN will start with a few bad data directories
(Part 1 of testing DiskChecker)
-
Key: HDFS-2111
URL:
[
https://issues.apache.org/jira/browse/HDFS-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J reopened HDFS-1454:
---
@Eli - Failed to actually verify the entire documents. Patch was intended to
only remove staging, but I
[
https://issues.apache.org/jira/browse/HDFS-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J resolved HDFS-1454.
---
Resolution: Fixed
Re-resolving per Todd's suggestion.
Opened: HDFS-2036
Update the documentation to
Revise the HDFS design documentation
Key: HDFS-2036
URL: https://issues.apache.org/jira/browse/HDFS-2036
Project: Hadoop HDFS
Issue Type: Improvement
Components: documentation
Affects
95 matches
Mail list logo
