[ 
https://issues.apache.org/jira/browse/YARN-11424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709382#comment-17709382
 ] 

ASF GitHub Bot commented on YARN-11424:
---------------------------------------

slfan1989 commented on PR #5363:
URL: https://github.com/apache/hadoop/pull/5363#issuecomment-1499065726

   @goiri This pr may not be able to clean bulid, I read this part of the code 
carefully. 
   
   The javac warning should be caused by a new proto code added to this pr. 
   
   ```
   message DeregisterSubClustersProto {
     optional string subClusterId = 1;
     optional string deregisterState = 2;
     optional string lastHeartBeatTime = 3;
     optional string information = 4;
     optional string subClusterState = 5;
   }
   ```
   This code will be directly compiled into `DeregisterSubClustersProto.java` 
by protobuf.
   
   ```
   hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api/target/
   
generated-sources/java/org/apache/hadoop/yarn/proto/YarnServerResourceManagerServiceProtos.java:18867:102:
   [deprecation] PARSER in DeregisterSubClustersProto has been deprecated
   ```
   
   We can check the following issue, the current version of protobuf does not 
seem to be able to solve it.
   https://github.com/protocolbuffers/protobuf/issues/7271




> [Federation] Router AdminCLI Supports DeregisterSubCluster.
> -----------------------------------------------------------
>
>                 Key: YARN-11424
>                 URL: https://issues.apache.org/jira/browse/YARN-11424
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: federation
>    Affects Versions: 3.4.0
>            Reporter: Shilun Fan
>            Assignee: Shilun Fan
>            Priority: Major
>              Labels: pull-request-available
>
> Router provides commands for Deregister SubCluster.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to