HDFS-Federation: Add support for multiple namenodes in MiniDFSCluster
--
Key: HDFS-1652
URL: https://issues.apache.org/jira/browse/HDFS-1652
Project: Hadoop HDFS
Issue Type
Block received is sent with invalid DatanodeRegistration
--
Key: HDFS-1653
URL: https://issues.apache.org/jira/browse/HDFS-1653
Project: Hadoop HDFS
Issue Type: Bug
Componen
[
https://issues.apache.org/jira/browse/HDFS-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas resolved HDFS-1653.
---
Resolution: Fixed
Hadoop Flags: [Reviewed]
Committed the patch. Thank you Tanping.
> B
[
https://issues.apache.org/jira/browse/HDFS-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas resolved HDFS-1645.
---
Resolution: Fixed
Hadoop Flags: [Reviewed]
I committed the patch
> DatanodeCommand Fina
Fix TestDFSUpgrade? and TestDFSRollback? failures.
---
Key: HDFS-1654
URL: https://issues.apache.org/jira/browse/HDFS-1654
Project: Hadoop HDFS
Issue Type: Sub-task
Components: test
Federation: DatablockScanner should scan blocks for all the block pools.
Key: HDFS-1655
URL: https://issues.apache.org/jira/browse/HDFS-1655
Project: Hadoop HDFS
Issue
getDelegationToken in HftpFileSystem should renew TGT if needed.
Key: HDFS-1656
URL: https://issues.apache.org/jira/browse/HDFS-1656
Project: Hadoop HDFS
Issue Type: Bug
Af
[
https://issues.apache.org/jira/browse/HDFS-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jitendra Nath Pandey resolved HDFS-1647.
Resolution: Fixed
Hadoop Flags: [Reviewed]
I committed it to the branch.
> Fe
[
https://issues.apache.org/jira/browse/HDFS-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas resolved HDFS-1639.
---
Resolution: Fixed
Hadoop Flags: [Reviewed]
I committed the patch.
> Add block pool mana
[
https://issues.apache.org/jira/browse/HDFS-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas resolved HDFS-1648.
---
Resolution: Fixed
Hadoop Flags: [Reviewed]
I committed the patch. Thank you Tanping.
>
Tests that corrupt block files fail due to changed block pool file path in
federation
-
Key: HDFS-1657
URL: https://issues.apache.org/jira/browse/HDFS-1657
Project: H
Hey folks,
Would those of you working on a branch mind adopting a naming convention for
all the federation tickets? I'm really glad to see all the changes going
upstream but it's getting confusing to separate out what are bugs that apply
to trunk vs bugs that are just due to the federation branch
+1
Looks like some of the relevant tickets are getting created with a prefix,
but not all. It'd be great if this got standardized.
--
Aaron T. Myers
Software Engineer, Cloudera
On Fri, Feb 25, 2011 at 2:53 PM, Todd Lipcon wrote:
> Hey folks,
>
> Would those of you working on a branch mind ad
A less expensive way to figure out directory size
-
Key: HDFS-1658
URL: https://issues.apache.org/jira/browse/HDFS-1658
Project: Hadoop HDFS
Issue Type: Improvement
Reporter: Hairon
Sounds good. We will make sure jiras created have Federation: prefix.
On Fri, Feb 25, 2011 at 2:55 PM, Aaron T. Myers wrote:
> +1
>
> Looks like some of the relevant tickets are getting created with a prefix,
> but not all. It'd be great if this got standardized.
>
> --
> Aaron T. Myers
> Softwa
Thanks Suresh!
-Todd
On Fri, Feb 25, 2011 at 3:40 PM, suresh srinivas wrote:
> Sounds good. We will make sure jiras created have Federation: prefix.
>
> On Fri, Feb 25, 2011 at 2:55 PM, Aaron T. Myers wrote:
>
>> +1
>>
>> Looks like some of the relevant tickets are getting created with a prefix
JIRA has this nice feature called 'Tag'. We've been using this for
Herriot development - seems much cleaner than clogging synopses field
with additional wodking.
--
Take care,
Konstantin (Cos) Boudnik
On Fri, Feb 25, 2011 at 14:53, Todd Lipcon wrote:
> Hey folks,
>
> Would those of you workin
HDFS Federation: BPOfferService exits after the first iteration of the loop
Key: HDFS-1659
URL: https://issues.apache.org/jira/browse/HDFS-1659
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas resolved HDFS-1657.
---
Resolution: Fixed
Hadoop Flags: [Reviewed]
I committed the patch.
> HDFS Federation: Te
HDFS Federation: Datanode doesn't start with two namenodes
--
Key: HDFS-1660
URL: https://issues.apache.org/jira/browse/HDFS-1660
Project: Hadoop HDFS
Issue Type: Sub-task
R
Hdfs Federation: Remove unnecessary TODO:FEDERATION comments.
-
Key: HDFS-1661
URL: https://issues.apache.org/jira/browse/HDFS-1661
Project: Hadoop HDFS
Issue Type: Bug
Affects
HDFS federation: fix unit test case, TestCheckpoint and TestDataNodeMXBean
--
Key: HDFS-1662
URL: https://issues.apache.org/jira/browse/HDFS-1662
Project: Hadoop HDFS
Is
HDFS federation: Rename getPoolId() everywhere to getBlockPoolId()
---
Key: HDFS-1663
URL: https://issues.apache.org/jira/browse/HDFS-1663
Project: Hadoop HDFS
Issue Type: Bug
HDFS federation :Add new
column
s of Block
Pool
Used
and
Block
Pool
Used
%
into JSP
Key: HDFS-1664
URL: https://issues.apache.org/jira/browse/HDFS-1664
Proj
[
https://issues.apache.org/jira/browse/HDFS-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas resolved HDFS-1650.
---
Resolution: Fixed
Hadoop Flags: [Reviewed]
I committed the patch. Thank you Tanping.
>
[
https://issues.apache.org/jira/browse/HDFS-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas resolved HDFS-1651.
---
Resolution: Fixed
Hadoop Flags: [Reviewed]
I committed the patch. Thank you Tanping.
>
Balancer sleeps inadequately
Key: HDFS-1665
URL: https://issues.apache.org/jira/browse/HDFS-1665
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Tsz Wo (Nicholas), SZE
Assignee: Tsz Wo (Nic
Having the naming convention that we use helps manage emails better due to
subject lines including "HDFS Federation". As far as tagging is concerned,
all federation jiras are subtasks of HDFS-1052. Hence some kind of grouping
can be done based on that.
On Fri, Feb 25, 2011 at 4:28 PM, Konstantin B
On Fri, Feb 25, 2011 at 9:47 PM, suresh srinivas wrote:
> Having the naming convention that we use helps manage emails better due to
> subject lines including "HDFS Federation". As far as tagging is concerned,
> all federation jiras are subtasks of HDFS-1052. Hence some kind of grouping
> can be d
Right, if you are looking into email filtering then tagging won't
help, I guess. So I guess your solution would work fine.
On Fri, Feb 25, 2011 at 21:47, suresh srinivas wrote:
> Having the naming convention that we use helps manage emails better due to
> subject lines including "HDFS Federation"
30 matches
Mail list logo