This is a reminder that we are branching Common, HDFS, and Map/Reduce
tomorrow (9/18) at 4:45pm PDT. After the branch, only critical bug
fixes can be put onto the branch without an explicit vote. The only
current exception is the HDFS append work, which is expected to take a
few more
The Hadoop PMC has voted to make Cos a QA committer on Common, HDFS,
and MapReduce. I'd like to welcome Cos as the newest committer.
-- Owen
I've committed HADOOP-5107 to Common and HDFS. MapReduce will follow
soon.
There are a couple of things that change:
1. The non-release version names move to the Maven-friendly 0.22.0-
SNAPSHOT instead of 0.22.0-dev.
2. To change Common and push it to your local Maven repository:
a. make
Your local storage should get used for MR. Use Lustre via file://
(LocalFileSystem, iirc)
instead of HDFS via hdfs:// (DistributedFileSystem, irrc) as the default file
system type.
If Lustre has integrated checksums, you'll want to use the
RawLocalFileSystem instead of LocalFileSystem.
On Mon, Sep 13, 2010 at 11:10 AM, Todd Lipcon t...@cloudera.com wrote:
Yep, but there are plenty of 10 node clusters out there that do important
work at small startups or single-use-case installations, too. We need to
provide scalability and security features that work for the 100+ node
On Mon, Oct 3, 2011 at 2:50 PM, Todd Lipcon t...@cloudera.com wrote:
In essence, that means that we would:
1) Ask contributors to provide patches against 0.20-security branch
instead of 0.20-append
+1
2) Move the branch itself into some kind of attic/ directory
You can just delete it.
To me, I'd much much rather have the human readable description of what is
being fixed and I mostly could care less about which subversion commit it
corresponds to. I'd be all for using the CHANGE.txt description as the
commit message for both trunk and the branches.
-- Owen
I disagree. Trunk should become branch-3 once someone wants to start
stabilizing it. Arun is going to need the minor versions for when he adds
features.
X.Y.Z
Z = bug fixes
Y = minor release (compatible, adds features)
X = major release (incompatible)
So from branch-2 will come branch-2.0 with
On Wed, Mar 28, 2012 at 12:32 PM, Todd Lipcon t...@cloudera.com wrote:
But new features also go to trunk. And if none of our new features are
incompatible, why do we anticipate that trunk is 3.0?
Let's imagine that we already had a 2.0.0 release. Now we want to add
features like HA. The only
On Wed, Mar 28, 2012 at 5:11 PM, Doug Cutting cutt...@apache.org wrote:
On 03/28/2012 12:39 PM, Owen O'Malley wrote:
[ ... ] So the RM of the 2 branch needs to make the call of what
should be 2.1 vs 3.0.
I thought these were community decisions, not RM decisions, no?
What to release
I think that using -(alpha,beta) tags on the release versions is a really
bad idea. All releases should follow the strictly numeric
(Major.Minor.Patch) pattern that we've used for all of the releases except
the 2.0.x ones.
-- Owen
On Mon, Feb 4, 2013 at 11:53 AM, Stack st...@duboce.net wrote:
On Tue, Jun 24, 2014 at 4:44 PM, Alejandro Abdelnur t...@cloudera.com
wrote:
After reading this thread and thinking a bit about it, I think it should be
OK such move up to JDK7 in Hadoop
I agree with Alejandro. Changing minimum JDKs is not an incompatible change
and is fine in the 2 branch.
All,
Haohui and I would like to pull code for an async io c++ hdfs client
from https://github.com/haohui/libhdfspp as a new development branch. The
motivation is to get a high performance asynchronous c++ hdfs client and
the driving need is to support reading ORC files from HDFS without a jvm
On Wed, Jan 27, 2016 at 9:59 AM, Gangumalla, Uma
wrote:
> I think Chimera goal is to enhance even for other use cases.
Naturally.
> For Hadoop, CTR mode should be enough today,
This isn't true. Hadoop should use better encryption for RPC and shuffle,
both of which
Sorry to be coming in to this discussion late. Rather than pull the code
out of Hadoop, may I suggest instead making it a separate subproject within
Hadoop itself? I'd suggest letting it release independently of Hadoop,
since it will need a much faster cadence that Hadoop proper does. It should
The DataWorks Summit EU 2017 (including Hadoop Summit) is going to be in
Munich April 5-6 2017
. I’ve pasted the text from the CFP below.
Would you like to share your knowledge with the best and brightest in the
data community? If so, we encourage you to submit an abstract for DataWorks
Summit
As we discussed in hdfs-dev@hadoop, I did a force push to Hadoop's trunk to
replace the Ozone merge with a rebase.
That means that you'll need to rebase your branches.
.. Owen
All,
Dataworks Summit San Jose 2018 is June 17-21. The call for abstracts is
open through February 9th. One of the tracks is Big Compute And Storage,
which is great for talks about Hadoop. You can submit an abstract at
https://dataworkssummit.com/san-jose-2018/
Thanks,
Owen
+1 (binding)
.. Owen
On Sun, Mar 11, 2018 at 6:20 PM, Chris Douglas wrote:
> +1 (binding) -C
>
> On Thu, Mar 8, 2018 at 9:31 AM, Jim Clampffer
> wrote:
> > Hi Everyone,
> >
> > The feedback was generally positive on the discussion thread [1] so
Hi Joep,
On Tue, Mar 6, 2018 at 6:50 PM, J. Rottinghuis
wrote:
Obviously when people do want to use Ozone, then having it in the same repo
> is easier. The flipside is that, separate top-level project in the same
> repo or not, it adds to the Hadoop releases.
>
Apache
This discussion seems to have died down coming closer consensus without a
resolution.
I'd like to propose the following compromise:
* HDSL become a subproject of Hadoop.
* HDSL will release separately from Hadoop. Hadoop releases will not
contain HDSL and vice versa.
* HDSL will get its own jira
Ok, with a lot of +1's, one +0, and no -1's the vote passes.
We have a new subproject!
We should resolve the final name and then create a jira instance for it.
Thanks everyone,
Owen
On Thu, Mar 22, 2018 at 11:09 AM, Lei Xu wrote:
>
> I have one concrete question about how this HDSL subproject being
> separated: Ozone / HDSL was designed in the current way to re-use the
> existing HDFS code base as much as possible, thus today for this
> container service
Andrew and Daryn,
Do you have any feedback on the proposal? Otherwise, we can start a vote
for "adoption of new codebase" tomorrow.
.. Owen
On Wed, Mar 14, 2018 at 1:50 PM, Owen O'Malley <owen.omal...@gmail.com>
wrote:
> This discussion seems to have died down coming close
On Tue, Mar 20, 2018 at 8:34 PM, 郑锴(铁杰) wrote:
> >>* HDSL become a subproject of Hadoop.
> I'm not compfortable with the HDSL name, as Konstantin mentioned. H-DSL
> looks like a DSL language at the first glance.
>
Let's start a separate thread about the name. My
All,
Following our discussions on the previous thread (Merging branch HDFS-7240
to trunk), I'd like to propose the following:
* HDSL become a subproject of Hadoop.
* HDSL will release separately from Hadoop. Hadoop releases will not
contain HDSL and vice versa.
* HDSL will get its own jira
I think it would be good to get this in sooner rather than later, but I
have some thoughts.
1. It is hard to tell what has changed. git rebase -i tells me the
branch has 722 commits. The rebase failed with a conflict. It would really
help if you rebased to current trunk.
2. I think
On Thu, Mar 1, 2018 at 11:03 PM, Andrew Wang
wrote:
Owen mentioned making a Hadoop subproject; we'd have to
> hash out what exactly this means (I assume a separate repo still managed by
> the Hadoop project), but I think we could make this work if it's more
> attractive
+1 on the merge. We've been using it on the trunk of ORC for a while. It
will be great to have it released by Hadoop.
.. Owen
On Thu, Mar 1, 2018 at 10:31 AM, Vinayakumar B
wrote:
> Definitely this would be great addition. Kudos to everyone's contributions.
>
> I am
*sigh*
I asked you guys to rebase this before merge. It is tempting to squash it
into a single commit.
.. Owen
On Wed, Apr 25, 2018 at 11:06 AM, Chris Douglas wrote:
> This really made a mess of trunk. Periodically merging trunk into the
> HDFS-7240 branch, then merging
sts.apache.org/thread.html/43cd65c6b6c3c0e8ac
>
> Thanks
> Xiaoyu
>
>
>
>
>
> *From: *Owen O'Malley <owen.omal...@gmail.com>
> *Date: *Wednesday, April 25, 2018 at 11:15 AM
> *To: *Chris Douglas <cdoug...@apache.org>
> *Cc: *Xiaoyu Yao <x...@horto
Since you don't have any Apache Members, I'll join to provide Apache
oversight.
.. Owen
On Fri, Sep 6, 2019 at 1:38 PM Owen O'Malley wrote:
> +1 for moving to a new project.
>
> On Sat, Aug 31, 2019 at 10:19 PM Wangda Tan wrote:
>
>> Hi all,
>>
>> As we discu
+1 for moving to a new project.
On Sat, Aug 31, 2019 at 10:19 PM Wangda Tan wrote:
> Hi all,
>
> As we discussed in the previous thread [1],
>
> I just moved the spin-off proposal to CWIKI and completed all TODO parts.
>
>
>
I'm very unhappy with this direction. In particular, I don't think git is a
good place for distribution of binary artifacts. Furthermore, the PMC
shouldn't be releasing anything without a release vote.
I'd propose that we make a third party module that contains the *source* of
the pom files to
I'm very -1 on adding these semantics.
When you create the table's directory, set the default ACL. That will have
exactly the effect that you are looking for without creating additional
semantics.
.. Owen
On Fri, Oct 16, 2020 at 7:02 PM Xinli shang wrote:
> Hi all,
>
> I opened
inue branc-2.10 ..? As rolling upgrade
> support is available from 2 to 3, any chance to upgrade to branch-3.X,so
> that so many features and improvements will be available..?
>
>
>> On Thu, 9 Dec 2021 at 5:55 AM, Owen O'Malley wrote:
>>
>> All,
>> I've started backp
All,
I've started backporting Router-Based Federation work from trunk back
into Hadoop 2.10. The goal is to backport everything that is relevant in
Hadoop 2. Would anyone outside of LinkedIn be interested in it?
Thanks,
Owen
We have a critical issue that has been occasionally crashing our NameNode's
with thread exhaustion. I'd love a review for the patch -
https://github.com/apache/hadoop/pull/4527
Thanks,
Owen
a small set of Hadoop users, moreover an even
> smaller subset of them will choose to use the mysql backend.
>
> (And there need to be instructions for how to acquire the mysql connector
> jar since it's not shipped in the convenience binary)
>
> On Thu, Jun 8, 2023 at 10:55 PM Owen
We are allowed to use category X software in optional components.
Furthermore, the dependency is marked as provided, so it won't be pulled
into a transitive closure.
You are right that I should have included a comment about that on the
original jira.
.. Owen
On Fri, Jun 9, 2023 at 1:58 AM
The relevant url is https://www.apache.org/legal/resolved.html#optional
On Fri, Jun 9, 2023 at 6:54 AM Owen O'Malley wrote:
> We are allowed to use category X software in optional components.
> Furthermore, the dependency is marked as provided, so it won't be pulled
> into a transitiv
Versions: 0.22.0
Reporter: Owen O'Malley
Assignee: Owen O'Malley
Fix For: 0.22.0
Currently the build is broken on trunk. The jar files need to be updated to the
current ones, along with the new version.
--
This message is automatically generated by JIRA.
-
You can
[
https://issues.apache.org/jira/browse/HDFS-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-638.
Resolution: Fixed
Suresh fixed this without a jira.
The build.xml refences jars that don't exist
Issue Type: Bug
Components: test
Affects Versions: 0.20.2
Reporter: Owen O'Malley
Assignee: Owen O'Malley
Priority: Blocker
Fix For: 0.21.0
Currently, we have a bad cycle where to build hdfs you need to test mapreduce
and iterate once
[
https://issues.apache.org/jira/browse/HDFS-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-641.
Resolution: Fixed
I just committed this.
Move all of the benchmarks and tests that depend
Make the versions of libraries consistent
-
Key: HDFS-787
URL: https://issues.apache.org/jira/browse/HDFS-787
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Owen O'Malley
Push HADOOP-6551 into HDFS
--
Key: HDFS-986
URL: https://issues.apache.org/jira/browse/HDFS-986
Project: Hadoop HDFS
Issue Type: Improvement
Reporter: Owen O'Malley
We need to throw readable error
Components: name-node
Reporter: Owen O'Malley
Assignee: Owen O'Malley
Currently some of the NameNode servlets use RPC to connect from the NameNode to
itself. They should do it more directly with the NameNode object.
--
This message is automatically generated
: tools
Reporter: Owen O'Malley
Assignee: Owen O'Malley
Attachments: fetchdt.patch
I would like to extend fetchdt to allow renewing and canceling tokens.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
[
https://issues.apache.org/jira/browse/HDFS-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-98.
---
Resolution: Won't Fix
Leaving the old FileSystem behavior and fixing it in FileContext is right
Reporter: Owen O'Malley
Assignee: Matt Foley
Fix For: 0.20.100
Current logging and metrics are insufficient to diagnose latency problems in
cluster startup. Add:
1. better logs in both Datanode and Namenode for Initial Block Report
processing, to help
: Bug
Reporter: Owen O'Malley
Assignee: Suresh Srinivas
Fix For: 0.20.203.0
Following tests are failing:
TestHDFSServerPorts
TestNNLeaseRecovery
TestSaveNamespace
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http
Remove duplicate jar entries from common
Key: HDFS-1810
URL: https://issues.apache.org/jira/browse/HDFS-1810
Project: Hadoop HDFS
Issue Type: Improvement
Reporter: Owen O'Malley
Create scripts to decommission datanodes
Key: HDFS-1811
URL: https://issues.apache.org/jira/browse/HDFS-1811
Project: Hadoop HDFS
Issue Type: Improvement
Reporter: Owen O'Malley
[
https://issues.apache.org/jira/browse/HDFS-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-1952.
-
Resolution: Fixed
Resolving this, since it was committed to trunk.
FSEditLog.open() appears
[
https://issues.apache.org/jira/browse/HDFS-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-1666.
-
Resolution: Fixed
Fix Version/s: 0.22.0
Assignee: Todd Lipcon
This was committed
[
https://issues.apache.org/jira/browse/HDFS-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-2328.
-
Resolution: Fixed
I committed this to 20-s and 205. I'll commit it to trunk as part of
MAPREDUCE
Components: build
Reporter: Owen O'Malley
Assignee: Owen O'Malley
When I first wrote the libhdfs autoconf/automake stuff, I incorrectly put my
email address in the AC_INIT line, which means if something goes wrong, you get:
{quote}
configure: WARNING: ## Report
[
https://issues.apache.org/jira/browse/HDFS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-224.
Resolution: Duplicate
We have a different version of harchives.
I propose a tool
Components: contrib/raid, scripts
Reporter: Owen O'Malley
Since we send the block tokens unencrypted to the datanode, we currently start
the datanode as root and get a secure ( 1024) port.
If we have the datanode generate a nonce and send it on the connection
Owen O'Malley created HDFS-3316:
---
Summary: The tar ball doesn't include jsvc any more
Key: HDFS-3316
URL: https://issues.apache.org/jira/browse/HDFS-3316
Project: Hadoop HDFS
Issue Type: Bug
Owen O'Malley created HDFS-3345:
---
Summary: Primary and secondary Principals must be the same
Key: HDFS-3345
URL: https://issues.apache.org/jira/browse/HDFS-3345
Project: Hadoop HDFS
Issue Type
Owen O'Malley created HDFS-3348:
---
Summary: After HDFS-2617 can't use 0.0.0.0 in dfs.http.address
Key: HDFS-3348
URL: https://issues.apache.org/jira/browse/HDFS-3348
Project: Hadoop HDFS
Issue
Owen O'Malley created HDFS-3374:
---
Summary: hdfs' TestDelegationToken fails intermittently with a
race condition
Key: HDFS-3374
URL: https://issues.apache.org/jira/browse/HDFS-3374
Project: Hadoop HDFS
Owen O'Malley created HDFS-3461:
---
Summary: HFTP should use the same port protocol for getting the
delegation token
Key: HDFS-3461
URL: https://issues.apache.org/jira/browse/HDFS-3461
Project: Hadoop
Owen O'Malley created HDFS-3466:
---
Summary: The SPNEGO filter for the NameNode should come out of the
web keytab file
Key: HDFS-3466
URL: https://issues.apache.org/jira/browse/HDFS-3466
Project: Hadoop
[
https://issues.apache.org/jira/browse/HDFS-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-2386.
-
Resolution: Invalid
Fixed via HDFS-2617.
with security enabled fsck calls lead
Owen O'Malley created HDFS-3749:
---
Summary: Disable check for jsvc on windows
Key: HDFS-3749
URL: https://issues.apache.org/jira/browse/HDFS-3749
Project: Hadoop HDFS
Issue Type: Bug
Owen O'Malley created HDFS-3993:
---
Summary: The KSSL class should not limit the ssl ciphers
Key: HDFS-3993
URL: https://issues.apache.org/jira/browse/HDFS-3993
Project: Hadoop HDFS
Issue Type
[
https://issues.apache.org/jira/browse/HDFS-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-4009.
-
Resolution: Won't Fix
This is a feature, not a bug.
In particular, if your kerberos ticket has 1
[
https://issues.apache.org/jira/browse/HDFS-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-4010.
-
Resolution: Won't Fix
They are used via the java ServiceLoader interface
[
https://issues.apache.org/jira/browse/HDFS-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-4011.
-
Resolution: Invalid
This is a feature.
WebHdfsFileSystem shouldn't implicitly
[
https://issues.apache.org/jira/browse/HDFS-4012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-4012.
-
Resolution: Not A Problem
This is not a problem.
HftpFileSystem shouldn't
[
https://issues.apache.org/jira/browse/HDFS-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-3983.
-
Resolution: Won't Fix
Target Version/s: (was: )
KSSL is deprecated and should never
[
https://issues.apache.org/jira/browse/HDFS-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-3699.
-
Resolution: Won't Fix
Using KSSL is strongly deprecated and should be avoided in secure clusters
Owen O'Malley created HDFS-8707:
---
Summary: Implement an async pure c++ HDFS client
Key: HDFS-8707
URL: https://issues.apache.org/jira/browse/HDFS-8707
Project: Hadoop HDFS
Issue Type: New
Owen O'Malley created HDFS-9025:
---
Summary: fix compilation issues on arch linux
Key: HDFS-9025
URL: https://issues.apache.org/jira/browse/HDFS-9025
Project: Hadoop HDFS
Issue Type: Sub-task
Owen O'Malley created HDFS-14244:
Summary: hdfs++ doesn't add necessary libraries to dynamic library
link
Key: HDFS-14244
URL: https://issues.apache.org/jira/browse/HDFS-14244
Project: Hadoop HDFS
Owen O'Malley created HDFS-16253:
Summary: Add a toString implementation to DFSInputStream
Key: HDFS-16253
URL: https://issues.apache.org/jira/browse/HDFS-16253
Project: Hadoop HDFS
Issue
Owen O'Malley created HDFS-16495:
Summary: RBF should prepend the client ip rather than append it.
Key: HDFS-16495
URL: https://issues.apache.org/jira/browse/HDFS-16495
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-16495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-16495.
--
Fix Version/s: 3.4.0
3.2.4
Resolution: Fixed
> RBF should prep
Owen O'Malley created HDFS-16517:
Summary: In 2.10 the distance metric is wrong for non-DN machines
Key: HDFS-16517
URL: https://issues.apache.org/jira/browse/HDFS-16517
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-16518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-16518.
--
Fix Version/s: 3.4.0
2.10.2
3.3.3
Resolution
[
https://issues.apache.org/jira/browse/HDFS-16517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-16517.
--
Fix Version/s: 2.10.2
Resolution: Fixed
> In 2.10 the distance metric is wrong for
Owen O'Malley created HDFS-16778:
Summary: Separate out the logger for which DN is picked by a
DFSInputStream
Key: HDFS-16778
URL: https://issues.apache.org/jira/browse/HDFS-16778
Project: Hadoop
[
https://issues.apache.org/jira/browse/HDFS-16767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-16767.
--
Fix Version/s: 3.4.0
3.3.9
Resolution: Fixed
I just committed
[
https://issues.apache.org/jira/browse/HDFS-16886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-16886.
--
Fix Version/s: 3.4.0
3.3.5
Resolution: Fixed
> Fix documentat
[
https://issues.apache.org/jira/browse/HDFS-16844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-16844.
--
Fix Version/s: 3.4.0
3.3.5
Resolution: Fixed
> [RBF] The rout
[
https://issues.apache.org/jira/browse/HDFS-16845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-16845.
--
Fix Version/s: 3.4.0
3.3.5
2.10.3
Resolution
[
https://issues.apache.org/jira/browse/HDFS-16847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-16847.
--
Fix Version/s: 3.4.0
3.3.5
Resolution: Fixed
I committed
[
https://issues.apache.org/jira/browse/HDFS-16851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-16851.
--
Fix Version/s: 3.3.6
3.4.0
Resolution: Fixed
> RBF: Add a util
Owen O'Malley created HDFS-16856:
Summary: [RBF] Refactor router admin command to use HDFS
AdminHelper class
Key: HDFS-16856
URL: https://issues.apache.org/jira/browse/HDFS-16856
Project: Hadoop HDFS
Owen O'Malley created HDFS-16843:
Summary: [RBF] The routers should be resiliant against exceptions
from StateStore
Key: HDFS-16843
URL: https://issues.apache.org/jira/browse/HDFS-16843
Project
[
https://issues.apache.org/jira/browse/HDFS-16836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-16836.
--
Fix Version/s: 3.4.0
3.3.5
Resolution: Fixed
I just committed
[
https://issues.apache.org/jira/browse/HDFS-16843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-16843.
--
Resolution: Duplicate
> [RBF] The routers should be resiliant against exceptions f
Owen O'Malley created HDFS-16844:
Summary: [RBF] The routers should be resiliant against exceptions
from StateStore
Key: HDFS-16844
URL: https://issues.apache.org/jira/browse/HDFS-16844
Project
Owen O'Malley created HDFS-16851:
Summary: [RBF] Utility to textually dump the StateStore
Key: HDFS-16851
URL: https://issues.apache.org/jira/browse/HDFS-16851
Project: Hadoop HDFS
Issue
[
https://issues.apache.org/jira/browse/HDFS-16877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-16877.
--
Fix Version/s: 3.4.0
Assignee: Simbarashe Dzinamarira
Resolution: Fixed
I've
[
https://issues.apache.org/jira/browse/HDFS-16917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-16917.
--
Fix Version/s: 3.4.0
Resolution: Fixed
> Add transfer rate quantile metr
[
https://issues.apache.org/jira/browse/HDFS-16901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-16901.
--
Fix Version/s: 3.4.0
3.3.6
Resolution: Fixed
Thanks, Simba!
>
1 - 100 of 102 matches
Mail list logo