Thanks for clarifying, Owen.
Should we have the bylaws somewhere on wiki?
--Konstantin
On Thu, Apr 28, 2011 at 1:33 PM, Owen O'Malley wrote:
> 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
HDFS-client may block shutdown of JVM
-
Key: HDFS-1868
URL: https://issues.apache.org/jira/browse/HDFS-1868
Project: Hadoop HDFS
Issue Type: Bug
Components: hdfs client
Affects Versions: 0.20
Owen, thanks for clarification.
I have attached the patch to the jira HDFS-1052. Please use the jira to cast
your vote or post objections. If you have objections please be specific on
how I can address it and move forward with this issue.
Regards,
Suresh
On Thu, Apr 28, 2011 at 1:33 PM, Owen O'M
Remove a datanode from cluster if include list is not empty and this datanode
is removed from both include and exclude lists
Key: HDFS-1867
[
https://issues.apache.org/jira/browse/HDFS-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas resolved HDFS-1414.
---
Resolution: Fixed
This has been addressed by other subtasks in HDFS-1052.
> HDFS federation :
[
https://issues.apache.org/jira/browse/HDFS-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas resolved HDFS-1398.
---
Resolution: Fixed
Fix Version/s: 0.23.0
This has been addressed by other subtasks of HD
[
https://issues.apache.org/jira/browse/HDFS-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suresh Srinivas resolved HDFS-1397.
---
Resolution: Fixed
This has been addressed by other subtasks in HDFS-1052.
> HDFS federation:
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
As Eli suggested, I have uploaded a new patch to the jira. Merging new trunk
changes and testing them took several hours! It passes all the tests except
two unit test failure. These failures do not happen on my machine - if this
is a real failure we will address them after merging the patch to the
+1. Having an open QE process would be a tremendous value-add to the
overall quality of the feature. Append was an exemplary development in
this sense. Would it be possible to have Federation test plan (if
exists) to be published along with the specs on the JIRA (similar to
HDFS-265) at least for t
10 matches
Mail list logo
