[
https://issues.apache.org/jira/browse/GOBBLIN-1308?focusedWorklogId=518293&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-518293
]
ASF GitHub Bot logged work on GOBBLIN-1308:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 01/Dec/20 05:38
Start Date: 01/Dec/20 05:38
Worklog Time Spent: 10m
Work Description: jhsenjaliya commented on a change in pull request #3157:
URL: https://github.com/apache/incubator-gobblin/pull/3157#discussion_r533084315
##########
File path:
gobblin-yarn/src/main/java/org/apache/gobblin/yarn/AbstractYarnAppSecurityManager.java
##########
@@ -117,7 +118,11 @@ protected void startUp() throws Exception {
this.loginExecutor.scheduleAtFixedRate(new Runnable() {
@Override
public void run() {
- loginAndScheduleTokenRenewal();
+ try {
+ loginAndScheduleTokenRenewal();
+ }catch(Exception e){
+ LOGGER.error("Error login using keytab, will continue the thread and
try next time.");
Review comment:
Sure
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 518293)
Time Spent: 1h 20m (was: 1h 10m)
> Gobblin's kerberos token management for remote clusters
> -------------------------------------------------------
>
> Key: GOBBLIN-1308
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1308
> Project: Apache Gobblin
> Issue Type: Improvement
> Affects Versions: 0.15.0
> Reporter: Jay Sen
> Priority: Major
> Fix For: 0.16.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Gobblin's hadoop tokens/ key management :
> Problem: Gobblin only maintains local cluster tokens when key management is
> enabled. and does not have capability to manage tokens for remote hadoop
> cluster. ( based on my conversation with many folks here, the token files can
> be made available externally. but that would require that external system
> running on cron or something )
> Solution: add remote cluster token management in Gobblin. where remote
> clusters key can be managed same way it manages the local clusters keys.
>
> Config looks like following
> ( Changes the enable.key.management config to key.management.enabled )
>
> {code:java}
> gobblin.hadoop.key.management {
> enabled = true
> remote.clusters = [ ${gobblin_sync_systems.hadoop_cluster1},
> ${gobblin_sync_systems.hadoop_cluster2} ]
> }
> // These Gobblin platform configurations can be moved to database for other
> use-cases, but this layout helps make the platform moduler for each
> connectors.
> gobblin_sync_systems {
> hadoop_cluster1 {
> // if Hadoop config path is specified, the FileSystem will be created based
> on all the xml config provided here, which has all the required info.
> hadoop_config_path = "file:///etc/hadoop_cluster1/hadoop/config"
> // If hadoop config path is not specified, you can still specify the
> speecific nodes for the specific type of tokens
> namenode_uri = ["hdfs://nn1.hadoop_cluster1.example.com:8020",
> "hdfs://nn2.hadoop_cluster1.example.com:8020"]
> kms_nodes = [ "kms1.hadoop_cluster1.example.com:9292",
> "kms2.hadoop_cluster1.example.com:9292" ]
> }
> hadoop_cluster2 {
> hadoop_config_path = "file:///etc/hadoop_cluster1/hadoop/config"
> namenode_uri = ["hdfs://nn1.hadoop_cluster2.example.com:8020",
> "hdfs://nn2.hadoop_cluster2.example.com:8020"]
> kms_nodes = [ "kms1.hadoop_cluster2.example.com:9292",
> "kms2.hadoop_cluster2.example.com:9292" ]
> }
> }{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
