You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Bryan Pendleton (JIRA)" <ji...@apache.org> on 2006/04/10 22:48:00 UTC
[jira] Created: (HADOOP-130) Should be able to specify "wide" or
"full" replication
Should be able to specify "wide" or "full" replication
------------------------------------------------------
Key: HADOOP-130
URL: http://issues.apache.org/jira/browse/HADOOP-130
Project: Hadoop
Type: Improvement
Components: dfs
Environment: N/A
Reporter: Bryan Pendleton
Priority: Minor
Should be able to specify that a file be "fully" or "widely" replicated, rather than an explicit replication count. This would be useful for job configuration and jar files, and probably other files whose use is wide enough to necessitate reducing latency to access them.
The current implementation will also complain if you specify replication that is wider than the system's maximum replication value, and has no facility to enable "full" replication should the number of datanodes exceed the current maximum settable value of 32k.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (HADOOP-130) Should be able to specify "wide" or
"full" replication
Posted by "Sameer Paranjpye (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-130?page=all ]
Sameer Paranjpye reassigned HADOOP-130:
---------------------------------------
Assign To: Konstantin Shvachko
> Should be able to specify "wide" or "full" replication
> ------------------------------------------------------
>
> Key: HADOOP-130
> URL: http://issues.apache.org/jira/browse/HADOOP-130
> Project: Hadoop
> Type: Improvement
> Components: dfs
> Versions: 0.2
> Environment: N/A
> Reporter: Bryan Pendleton
> Assignee: Konstantin Shvachko
> Priority: Minor
> Fix For: 0.3
>
> Should be able to specify that a file be "fully" or "widely" replicated, rather than an explicit replication count. This would be useful for job configuration and jar files, and probably other files whose use is wide enough to necessitate reducing latency to access them.
> The current implementation will also complain if you specify replication that is wider than the system's maximum replication value, and has no facility to enable "full" replication should the number of datanodes exceed the current maximum settable value of 32k.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-130) Should be able to specify "wide" or
"full" replication
Posted by "Sameer Paranjpye (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-130?page=all ]
Sameer Paranjpye updated HADOOP-130:
------------------------------------
Fix Version: 0.3
Version: 0.2
> Should be able to specify "wide" or "full" replication
> ------------------------------------------------------
>
> Key: HADOOP-130
> URL: http://issues.apache.org/jira/browse/HADOOP-130
> Project: Hadoop
> Type: Improvement
> Components: dfs
> Versions: 0.2
> Environment: N/A
> Reporter: Bryan Pendleton
> Priority: Minor
> Fix For: 0.3
>
> Should be able to specify that a file be "fully" or "widely" replicated, rather than an explicit replication count. This would be useful for job configuration and jar files, and probably other files whose use is wide enough to necessitate reducing latency to access them.
> The current implementation will also complain if you specify replication that is wider than the system's maximum replication value, and has no facility to enable "full" replication should the number of datanodes exceed the current maximum settable value of 32k.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-130) Should be able to specify "wide" or
"full" replication
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-130?page=all ]
Doug Cutting updated HADOOP-130:
--------------------------------
Fix Version: 0.5.0
(was: 0.4.0)
> Should be able to specify "wide" or "full" replication
> ------------------------------------------------------
>
> Key: HADOOP-130
> URL: http://issues.apache.org/jira/browse/HADOOP-130
> Project: Hadoop
> Type: Improvement
> Components: dfs
> Versions: 0.2.0
> Environment: N/A
> Reporter: Bryan Pendleton
> Assignee: Konstantin Shvachko
> Priority: Minor
> Fix For: 0.5.0
>
> Should be able to specify that a file be "fully" or "widely" replicated, rather than an explicit replication count. This would be useful for job configuration and jar files, and probably other files whose use is wide enough to necessitate reducing latency to access them.
> The current implementation will also complain if you specify replication that is wider than the system's maximum replication value, and has no facility to enable "full" replication should the number of datanodes exceed the current maximum settable value of 32k.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (HADOOP-130) Should be able to specify "wide" or
"full" replication
Posted by "Konstantin Shvachko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Shvachko resolved HADOOP-130.
----------------------------------------
Resolution: Duplicate
> Should be able to specify "wide" or "full" replication
> ------------------------------------------------------
>
> Key: HADOOP-130
> URL: https://issues.apache.org/jira/browse/HADOOP-130
> Project: Hadoop
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.2.0
> Environment: N/A
> Reporter: Bryan Pendleton
> Assignee: Konstantin Shvachko
> Priority: Minor
>
> Should be able to specify that a file be "fully" or "widely" replicated, rather than an explicit replication count. This would be useful for job configuration and jar files, and probably other files whose use is wide enough to necessitate reducing latency to access them.
> The current implementation will also complain if you specify replication that is wider than the system's maximum replication value, and has no facility to enable "full" replication should the number of datanodes exceed the current maximum settable value of 32k.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-130) Should be able to specify "wide" or
"full" replication
Posted by "Sameer Paranjpye (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HADOOP-130?page=all ]
Sameer Paranjpye updated HADOOP-130:
------------------------------------
Fix Version: 0.4
(was: 0.3)
> Should be able to specify "wide" or "full" replication
> ------------------------------------------------------
>
> Key: HADOOP-130
> URL: http://issues.apache.org/jira/browse/HADOOP-130
> Project: Hadoop
> Type: Improvement
> Components: dfs
> Versions: 0.2
> Environment: N/A
> Reporter: Bryan Pendleton
> Assignee: Konstantin Shvachko
> Priority: Minor
> Fix For: 0.4
>
> Should be able to specify that a file be "fully" or "widely" replicated, rather than an explicit replication count. This would be useful for job configuration and jar files, and probably other files whose use is wide enough to necessitate reducing latency to access them.
> The current implementation will also complain if you specify replication that is wider than the system's maximum replication value, and has no facility to enable "full" replication should the number of datanodes exceed the current maximum settable value of 32k.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira