his case, RBF is used by 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,
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
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 Wei-C
[
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 met
[
https://issues.apache.org/jira/browse/HDFS-16890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-16890.
--
Fix Version/s: 3.4.0
3.3.6
Resolution: Fixed
> RBF: Add peri
[
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!
[
https://issues.apache.org/jira/browse/HDFS-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-16895.
--
Fix Version/s: 3.4.0
3.3.5
Assignee: Hector Sandoval Cha
[
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 documenta
[
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
[
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 ut
[
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-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
Resol
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
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
[
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
[
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 excepti
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
Pr
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
Pr
[
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
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: H
[
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
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
[
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
Resol
[
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
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
[
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
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
anc-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 sta
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
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
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 https://issues.
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 bui
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,
>>
>&
+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.
>
>
> https://cwiki.apache.org/confluence/display/HADOOP/Submarine+Project+Sp
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: H
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
>
> Thanks
> Xiaoyu
>
>
>
>
>
> *From: *Owen O'Malley
> *Date: *Wednesday, April 25, 2018 at 11:15 AM
> *To: *Chris Douglas
> *Cc: *Xiaoyu Yao , Jitendra Pandey <
> jiten...@hortonworks.com>, Hdfs-dev
> *Subject: *Re: [RESULT][VOTE] Merge HDDS
*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 the whole thing back, c
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 is in DataNode itsel
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 general guidance on naming
things
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 instan
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
wrote:
> This discussion seems to have died down coming closer consensus without a
>
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
+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 I'd
> > like to start a formal vote for merging H
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 projects are about the gro
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 than incubation or a new T
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 Ozo
+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 not a C++ expert. So cannot
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
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 wi
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 should not use CTR.
> I
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
als
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
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 in
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
On Tue, Jun 24, 2014 at 4:44 PM, Alejandro Abdelnur
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. (Although I think
[
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 secur
[
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 sh
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 wrote:
> On Mon, Feb 4
[
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 s
[
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'
[
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
[
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 ti
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
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
Changing the configurations is a big and very touchy job. It is touchy in
that it is very exposed to the users and many many applications assume the
configuration is dealt with in particular ways. It is a requirement to
maintain compatibility and thus that needs to be factored in to the work.
Furth
[
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 ca
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: H
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
Projec
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: H
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
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
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
On Wed, Mar 28, 2012 at 5:11 PM, Doug Cutting 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?
>
On Wed, Mar 28, 2012 at 12:32 PM, Todd Lipcon 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 place to put that
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 t
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
ement
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 conne
[
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 propos
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: #
Reporter: Owen O'Malley
Assignee: Owen O'Malley
Fix For: 0.23.0
When looking for hdfs delegation tokens, Hftp converts the service to a string
and compares it to a text.
--
This message is automatically generated by JIRA.
If you think it was sent i
On Mon, Oct 3, 2011 at 2:50 PM, Todd Lipcon 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. Subversion always k
[
https://issues.apache.org/jira/browse/HDFS-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-2257.
-
Resolution: Not A Problem
HFTP already has a getDelegationToken, which it overrides
[
https://issues.apache.org/jira/browse/HDFS-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-2326.
-
Resolution: Invalid
Fix Version/s: (was: 0.20.205.0)
> hftp token rene
[
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
: Owen O'Malley
The rpm for hdfs should only require the same major version (eg. 0.23) of
common.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[
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 comm
[
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() ap
On Apr 27, 2011, at 10:12 PM, Konstantin Shvachko wrote:
> The question is whether this is a
> * Code Change,
> which requires Lazy consensus of active committers or a
> * Adoption of New Codebase,
> which needs Lazy 2/3 majority of PMC members
This is a code change, just like all of our jiras. T
On Apr 26, 2011, at 11:34 PM, suresh srinivas wrote:
>> 2. I assume that merging requires a vote. I am sure people who know bylaws
>> better than I do will correct me if it is not true.
>> Did I miss the vote?
>>
>
>
> As regards to voting, since I was not sure about the procedure, I had
> cons
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'M
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'M
: 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:
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
[
https://issues.apache.org/jira/browse/HDFS-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley resolved HDFS-1192.
-
Resolution: Fixed
Fix Version/s: 0.22.0
Hadoop Flags: [Reviewed]
This jira w
On Mon, Sep 13, 2010 at 11:10 AM, Todd Lipcon 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
> clusters but also no
On Mon, Sep 13, 2010 at 10:05 AM, Todd Lipcon wrote:
> This is not MR-specific, since the strangely named hadoop.job.ugi determines
> HDFS permissions as well.
Yeah, after I hit send, I realized that I should have used common-dev.
This is really a dev issue.
> "or the user must write a custom g
[
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 FileContex
> 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.
1 - 100 of 123 matches
Mail list logo
