Nanda kumar commented on HDFS-13333:

Thanks [~GeLiXin] for the work.
I'm thinking of introducing a new interface for HddsService plugins so that we 
can have more fine-grained control over how the plugin is initialized, started 
and stopped by {{HddsDatanodeService}}. With this new interface, we can define 
new exception(s) which will be thrown in case of failure and 
{{HddsDatanodeService}} can decide if it can proceed when it is not able to 
start the plugin.

The new plugin will look something like:
public interface HddsServicePlugin {
  void init() throws ServiceInitializationException;
  void start(Object service) throws ServiceException;
  void stop() throws IOException;
cc: [~xyao] [~anu]

> Ozone: Introduce a new SCM Exception which will be thrown when mandatory 
> property is missing 
> ---------------------------------------------------------------------------------------------
>                 Key: HDFS-13333
>                 URL: https://issues.apache.org/jira/browse/HDFS-13333
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ozone
>            Reporter: Nanda kumar
>            Assignee: LiXin Ge
>            Priority: Major
>              Labels: newbie
>         Attachments: HDFS-13333-HDFS-7240.001.patch, 
> HDFS-13333-HDFS-7240.002.patch, HDFS-13333-HDFS-7240.003.patch, 
> HDFS-13333.001.patch
> It's better to have a separate SCM Exception to indicate a missing mandatory 
> property. This was proposed by [~xyao] in  [this comment| 
> https://issues.apache.org/jira/browse/HDFS-13300?focusedCommentId=16408553&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16408553]

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to