[
https://issues.apache.org/jira/browse/HDFS-13832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16583701#comment-16583701
]
Ayush Saxena commented on HDFS-13832:
-------------------------------------
Thanks [~SouryakantaDwivedy] for putting up the issue.
We cannot simply remove the policy without checking whether there are any files
using that policy or not and if we do so and if there are files using that EC
policy we wont be able to read those files too
HDFS-12405 is already raised to counter the problem of safely removing an EC
policy.It will solve your purpose too.
> EC: No administrative command provided to delete an user-defined erasure
> coding policy
> --------------------------------------------------------------------------------------
>
> Key: HDFS-13832
> URL: https://issues.apache.org/jira/browse/HDFS-13832
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: erasure-coding
> Affects Versions: 3.0.0
> Environment: 3 node SUSE linux cluster
> Reporter: Souryakanta Dwivedy
> Assignee: Ayush Saxena
> Priority: Major
> Attachments: Delete_ec_policy.PNG
>
>
> No administrative command provided to delete an user defined erasure coding
> policy
> Step : -
> ---------------
> * Create a Directory
> - Add 64 user-defined ec policies in the ID range of [64 to 127].Beyond that
> system will not allow
> to add any more policy.
> - Enable an ec policy and the set it to the directory.
> - Disable the policy and check the state of the policy in -listPolicies
> -If the ec policy is in disable state ,system will not allow you to set it
> on any directory
> -Remove the ec policy and check the state of the policy in -listPolicies.
> Its just set the state as removed ,but the policy is still present in the
> list.
> -If the ec policy is in remove state,system will not allow you to set it on
> any directory
> - There is no difference between disable and remove state.
> -After adding 64 user-defined ec policies ,if an user wants to delete a
> policy which is not usable any more or not correctly added instead of that
> wants to add a new desired user-defined ec policy ,it can not be possible as
> no delete option is provided.Only remove policy option is given,which is not
> removing an user-defined policy,only set the policy state as removed.
> Actual ouput :-
>
> No administrative command provided to delete an user defined erasure coding
> policy.With "-removePolicy" we can set a policy state as removed,we cann't
> delete the user-defined ec policy.After adding 64 user-defined ec policies,if
> a user wants to delete an policy and add a new desired policy,there is no
> administrative provision provided to perform this operation.
>
> Expected output :-
>
> Either "-removePolicy" should remove the user-defined ec policy ,instead of
> changing the policy state to removed only or administrative privilege should
> be provided to delete an user-defined ec policy.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
