[jira] [Work logged] (HDFS-15960) Router NamenodeHeartbeatService fails to authenticate with namenode in a kerberized envi
[
https://issues.apache.org/jira/browse/HDFS-15960?focusedWorklogId=606673=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-606673
]
ASF GitHub Bot logged work on HDFS-15960:
-
Author: ASF GitHub Bot
Created on: 04/Jun/21 08:11
Start Date: 04/Jun/21 08:11
Worklog Time Spent: 10m
Work Description: goiri commented on a change in pull request #2887:
URL: https://github.com/apache/hadoop/pull/2887#discussion_r644478595
##
File path:
hadoop-hdfs-project/hadoop-hdfs-rbf/src/main/java/org/apache/hadoop/hdfs/server/federation/router/NamenodeHeartbeatService.java
##
@@ -170,7 +172,20 @@ protected void serviceInit(Configuration configuration)
throws Exception {
@Override
public void periodicInvoke() {
-updateState();
+try {
+ SecurityUtil.doAsCurrentUser(
+ new PrivilegedExceptionAction() {
+@Override
+public Object run() {
+ updateState();
+ return null;
+}
+ });
+} catch (IOException e) {
+ // Generic error that we don't know about
+ LOG.error("Unexpected exception while communicating with {}: {}",
Review comment:
#3 sounds reasonable, do you mind giving it a try in this PR?
--
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:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 606673)
Time Spent: 1.5h (was: 1h 20m)
> Router NamenodeHeartbeatService fails to authenticate with namenode in a
> kerberized envi
>
>
> Key: HDFS-15960
> URL: https://issues.apache.org/jira/browse/HDFS-15960
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Borislav Iordanov
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> We use http.hadoop.authentication.type = "kerberos" and when the
> NamenodeHeartbeatService calls the namenode via JMX, it is not providing a
> user security context so the authentication token is not transmitted and it
> fails.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Work logged] (HDFS-15960) Router NamenodeHeartbeatService fails to authenticate with namenode in a kerberized envi
[
https://issues.apache.org/jira/browse/HDFS-15960?focusedWorklogId=605654=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-605654
]
ASF GitHub Bot logged work on HDFS-15960:
-
Author: ASF GitHub Bot
Created on: 03/Jun/21 04:40
Start Date: 03/Jun/21 04:40
Worklog Time Spent: 10m
Work Description: goiri commented on a change in pull request #2887:
URL: https://github.com/apache/hadoop/pull/2887#discussion_r644478595
##
File path:
hadoop-hdfs-project/hadoop-hdfs-rbf/src/main/java/org/apache/hadoop/hdfs/server/federation/router/NamenodeHeartbeatService.java
##
@@ -170,7 +172,20 @@ protected void serviceInit(Configuration configuration)
throws Exception {
@Override
public void periodicInvoke() {
-updateState();
+try {
+ SecurityUtil.doAsCurrentUser(
+ new PrivilegedExceptionAction() {
+@Override
+public Object run() {
+ updateState();
+ return null;
+}
+ });
+} catch (IOException e) {
+ // Generic error that we don't know about
+ LOG.error("Unexpected exception while communicating with {}: {}",
Review comment:
#3 sounds reasonable, do you mind giving it a try in this PR?
--
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:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 605654)
Time Spent: 1h 20m (was: 1h 10m)
> Router NamenodeHeartbeatService fails to authenticate with namenode in a
> kerberized envi
>
>
> Key: HDFS-15960
> URL: https://issues.apache.org/jira/browse/HDFS-15960
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Borislav Iordanov
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> We use http.hadoop.authentication.type = "kerberos" and when the
> NamenodeHeartbeatService calls the namenode via JMX, it is not providing a
> user security context so the authentication token is not transmitted and it
> fails.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Work logged] (HDFS-15960) Router NamenodeHeartbeatService fails to authenticate with namenode in a kerberized envi
[
https://issues.apache.org/jira/browse/HDFS-15960?focusedWorklogId=605505=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-605505
]
ASF GitHub Bot logged work on HDFS-15960:
-
Author: ASF GitHub Bot
Created on: 02/Jun/21 20:05
Start Date: 02/Jun/21 20:05
Worklog Time Spent: 10m
Work Description: bolerio commented on a change in pull request #2887:
URL: https://github.com/apache/hadoop/pull/2887#discussion_r644283148
##
File path:
hadoop-hdfs-project/hadoop-hdfs-rbf/src/main/java/org/apache/hadoop/hdfs/server/federation/router/NamenodeHeartbeatService.java
##
@@ -170,7 +172,20 @@ protected void serviceInit(Configuration configuration)
throws Exception {
@Override
public void periodicInvoke() {
-updateState();
+try {
+ SecurityUtil.doAsCurrentUser(
+ new PrivilegedExceptionAction() {
+@Override
+public Object run() {
+ updateState();
+ return null;
+}
+ });
+} catch (IOException e) {
+ // Generic error that we don't know about
+ LOG.error("Unexpected exception while communicating with {}: {}",
Review comment:
Hi @goiri , following up this. I was able to create a unit test that
reproduces the problem and demonstrate that the patch fixes it. However, there
is a challenge.
The failure is when the router calls the JMX endpoint which returns some
info stats in addition to the basic alive status which is obtained in a
separate RPC call. The failure is soft - logs the exception and continues,
without the information it tried to obtain. However that information is needed
later during load balancing, which is how the original bug was discovered.
Now, because the main interface capturing knowledge about a NN on the router
side (FederationNamenodeContext) does not contain these stats, there is no way
to write a unit test against it. There are some unit tests in that area that
mock this interface and I modified the mock to include stats, but then I have
to downcast to the mock object in the test which is very ugly.
So the options are: (1) accept this ugly downcast (2) don't write the test
and eventually if Hadoop has an integration test suite, cover the use case
there and (3) modify the FederationNamenodeContext to include the stats (see
MembershipState and MembershipStats class). My vote would be for (3) as those
stats seem essential to the operation of a federated cluster. It would be ok
not to make all of the numbers part of the public interface, but the fact that
we need stats about resource utilization should be part of the interface.
--
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:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 605505)
Time Spent: 1h 10m (was: 1h)
> Router NamenodeHeartbeatService fails to authenticate with namenode in a
> kerberized envi
>
>
> Key: HDFS-15960
> URL: https://issues.apache.org/jira/browse/HDFS-15960
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Borislav Iordanov
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> We use http.hadoop.authentication.type = "kerberos" and when the
> NamenodeHeartbeatService calls the namenode via JMX, it is not providing a
> user security context so the authentication token is not transmitted and it
> fails.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Work logged] (HDFS-15960) Router NamenodeHeartbeatService fails to authenticate with namenode in a kerberized envi
[
https://issues.apache.org/jira/browse/HDFS-15960?focusedWorklogId=595836=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-595836
]
ASF GitHub Bot logged work on HDFS-15960:
-
Author: ASF GitHub Bot
Created on: 13/May/21 03:54
Start Date: 13/May/21 03:54
Worklog Time Spent: 10m
Work Description: Hexiaoqiao commented on a change in pull request #2887:
URL: https://github.com/apache/hadoop/pull/2887#discussion_r631544089
##
File path:
hadoop-hdfs-project/hadoop-hdfs-rbf/src/main/java/org/apache/hadoop/hdfs/server/federation/router/NamenodeHeartbeatService.java
##
@@ -170,7 +172,20 @@ protected void serviceInit(Configuration configuration)
throws Exception {
@Override
public void periodicInvoke() {
-updateState();
+try {
+ SecurityUtil.doAsCurrentUser(
+ new PrivilegedExceptionAction() {
Review comment:
Thanks @goiri and @bolerio for your comments. I am just concern if is it
necessary to do as current user here because Router has login when start daemon
and it is already execute with current login user. Do you meet some exception
here? Thanks.
--
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:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 595836)
Time Spent: 1h (was: 50m)
> Router NamenodeHeartbeatService fails to authenticate with namenode in a
> kerberized envi
>
>
> Key: HDFS-15960
> URL: https://issues.apache.org/jira/browse/HDFS-15960
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Borislav Iordanov
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> We use http.hadoop.authentication.type = "kerberos" and when the
> NamenodeHeartbeatService calls the namenode via JMX, it is not providing a
> user security context so the authentication token is not transmitted and it
> fails.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Work logged] (HDFS-15960) Router NamenodeHeartbeatService fails to authenticate with namenode in a kerberized envi
[
https://issues.apache.org/jira/browse/HDFS-15960?focusedWorklogId=595516=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-595516
]
ASF GitHub Bot logged work on HDFS-15960:
-
Author: ASF GitHub Bot
Created on: 12/May/21 18:27
Start Date: 12/May/21 18:27
Worklog Time Spent: 10m
Work Description: bolerio commented on a change in pull request #2887:
URL: https://github.com/apache/hadoop/pull/2887#discussion_r631301512
##
File path:
hadoop-hdfs-project/hadoop-hdfs-rbf/src/main/java/org/apache/hadoop/hdfs/server/federation/router/NamenodeHeartbeatService.java
##
@@ -170,7 +172,20 @@ protected void serviceInit(Configuration configuration)
throws Exception {
@Override
public void periodicInvoke() {
-updateState();
+try {
+ SecurityUtil.doAsCurrentUser(
+ new PrivilegedExceptionAction() {
+@Override
+public Object run() {
+ updateState();
+ return null;
+}
+ });
+} catch (IOException e) {
+ // Generic error that we don't know about
+ LOG.error("Unexpected exception while communicating with {}: {}",
Review comment:
Ok, will try to create one. Thanks for checking this out @goiri ,
somehow I missed the notification re your comments, Will follow up with a unit
test soon.
--
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:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 595516)
Time Spent: 50m (was: 40m)
> Router NamenodeHeartbeatService fails to authenticate with namenode in a
> kerberized envi
>
>
> Key: HDFS-15960
> URL: https://issues.apache.org/jira/browse/HDFS-15960
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Borislav Iordanov
>Priority: Major
> Labels: pull-request-available
> Time Spent: 50m
> Remaining Estimate: 0h
>
> We use http.hadoop.authentication.type = "kerberos" and when the
> NamenodeHeartbeatService calls the namenode via JMX, it is not providing a
> user security context so the authentication token is not transmitted and it
> fails.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Work logged] (HDFS-15960) Router NamenodeHeartbeatService fails to authenticate with namenode in a kerberized envi
[
https://issues.apache.org/jira/browse/HDFS-15960?focusedWorklogId=595514=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-595514
]
ASF GitHub Bot logged work on HDFS-15960:
-
Author: ASF GitHub Bot
Created on: 12/May/21 18:24
Start Date: 12/May/21 18:24
Worklog Time Spent: 10m
Work Description: bolerio commented on a change in pull request #2887:
URL: https://github.com/apache/hadoop/pull/2887#discussion_r631299899
##
File path:
hadoop-hdfs-project/hadoop-hdfs-rbf/src/main/java/org/apache/hadoop/hdfs/server/federation/router/NamenodeHeartbeatService.java
##
@@ -170,7 +172,20 @@ protected void serviceInit(Configuration configuration)
throws Exception {
@Override
public void periodicInvoke() {
-updateState();
+try {
+ SecurityUtil.doAsCurrentUser(
+ new PrivilegedExceptionAction() {
Review comment:
Sure, agreed that'll be more readable here.
--
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:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 595514)
Time Spent: 40m (was: 0.5h)
> Router NamenodeHeartbeatService fails to authenticate with namenode in a
> kerberized envi
>
>
> Key: HDFS-15960
> URL: https://issues.apache.org/jira/browse/HDFS-15960
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Borislav Iordanov
>Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> We use http.hadoop.authentication.type = "kerberos" and when the
> NamenodeHeartbeatService calls the namenode via JMX, it is not providing a
> user security context so the authentication token is not transmitted and it
> fails.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Work logged] (HDFS-15960) Router NamenodeHeartbeatService fails to authenticate with namenode in a kerberized envi
[
https://issues.apache.org/jira/browse/HDFS-15960?focusedWorklogId=580360=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-580360
]
ASF GitHub Bot logged work on HDFS-15960:
-
Author: ASF GitHub Bot
Created on: 09/Apr/21 21:49
Start Date: 09/Apr/21 21:49
Worklog Time Spent: 10m
Work Description: goiri commented on a change in pull request #2887:
URL: https://github.com/apache/hadoop/pull/2887#discussion_r610921207
##
File path:
hadoop-hdfs-project/hadoop-hdfs-rbf/src/main/java/org/apache/hadoop/hdfs/server/federation/router/NamenodeHeartbeatService.java
##
@@ -170,7 +172,20 @@ protected void serviceInit(Configuration configuration)
throws Exception {
@Override
public void periodicInvoke() {
-updateState();
+try {
+ SecurityUtil.doAsCurrentUser(
+ new PrivilegedExceptionAction() {
Review comment:
Can this be a lambda?
##
File path:
hadoop-hdfs-project/hadoop-hdfs-rbf/src/main/java/org/apache/hadoop/hdfs/server/federation/router/NamenodeHeartbeatService.java
##
@@ -170,7 +172,20 @@ protected void serviceInit(Configuration configuration)
throws Exception {
@Override
public void periodicInvoke() {
-updateState();
+try {
+ SecurityUtil.doAsCurrentUser(
+ new PrivilegedExceptionAction() {
+@Override
+public Object run() {
+ updateState();
+ return null;
+}
+ });
+} catch (IOException e) {
+ // Generic error that we don't know about
+ LOG.error("Unexpected exception while communicating with {}: {}",
Review comment:
Can we have a unit test for this?
--
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:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 580360)
Time Spent: 0.5h (was: 20m)
> Router NamenodeHeartbeatService fails to authenticate with namenode in a
> kerberized envi
>
>
> Key: HDFS-15960
> URL: https://issues.apache.org/jira/browse/HDFS-15960
> Project: Hadoop HDFS
> Issue Type: Bug
>Reporter: Borislav Iordanov
>Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> We use http.hadoop.authentication.type = "kerberos" and when the
> NamenodeHeartbeatService calls the namenode via JMX, it is not providing a
> user security context so the authentication token is not transmitted and it
> fails.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Work logged] (HDFS-15960) Router NamenodeHeartbeatService fails to authenticate with namenode in a kerberized envi
[
https://issues.apache.org/jira/browse/HDFS-15960?focusedWorklogId=580207=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-580207
]
ASF GitHub Bot logged work on HDFS-15960:
-
Author: ASF GitHub Bot
Created on: 09/Apr/21 17:56
Start Date: 09/Apr/21 17:56
Worklog Time Spent: 10m
Work Description: hadoop-yetus commented on pull request #2887:
URL: https://github.com/apache/hadoop/pull/2887#issuecomment-816855180
:broken_heart: **-1 overall**
| Vote | Subsystem | Runtime | Logfile | Comment |
|::|--:|:|::|:---:|
| +0 :ok: | reexec | 0m 34s | | Docker mode activated. |
_ Prechecks _ |
| +1 :green_heart: | dupname | 0m 0s | | No case conflicting files
found. |
| +0 :ok: | codespell | 0m 0s | | codespell was not available. |
| +1 :green_heart: | @author | 0m 0s | | The patch does not contain
any @author tags. |
| -1 :x: | test4tests | 0m 0s | | The patch doesn't appear to include
any new or modified tests. Please justify why no new tests are needed for this
patch. Also please list what manual steps were performed to verify this patch.
|
_ trunk Compile Tests _ |
| +1 :green_heart: | mvninstall | 34m 39s | | trunk passed |
| +1 :green_heart: | compile | 0m 41s | | trunk passed with JDK
Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 |
| +1 :green_heart: | compile | 0m 35s | | trunk passed with JDK
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08 |
| +1 :green_heart: | checkstyle | 0m 26s | | trunk passed |
| +1 :green_heart: | mvnsite | 0m 44s | | trunk passed |
| +1 :green_heart: | javadoc | 0m 36s | | trunk passed with JDK
Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 |
| +1 :green_heart: | javadoc | 0m 58s | | trunk passed with JDK
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08 |
| +1 :green_heart: | spotbugs | 1m 20s | | trunk passed |
| +1 :green_heart: | shadedclient | 14m 32s | | branch has no errors
when building and testing our client artifacts. |
_ Patch Compile Tests _ |
| +1 :green_heart: | mvninstall | 0m 33s | | the patch passed |
| +1 :green_heart: | compile | 0m 34s | | the patch passed with JDK
Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 |
| +1 :green_heart: | javac | 0m 34s | | the patch passed |
| +1 :green_heart: | compile | 0m 29s | | the patch passed with JDK
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08 |
| +1 :green_heart: | javac | 0m 29s | | the patch passed |
| +1 :green_heart: | blanks | 0m 0s | | The patch has no blanks
issues. |
| +1 :green_heart: | checkstyle | 0m 18s | | the patch passed |
| +1 :green_heart: | mvnsite | 0m 33s | | the patch passed |
| +1 :green_heart: | javadoc | 0m 31s | | the patch passed with JDK
Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 |
| +1 :green_heart: | javadoc | 0m 46s | | the patch passed with JDK
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08 |
| +1 :green_heart: | spotbugs | 1m 20s | | the patch passed |
| +1 :green_heart: | shadedclient | 14m 48s | | patch has no errors
when building and testing our client artifacts. |
_ Other Tests _ |
| -1 :x: | unit | 17m 48s |
[/patch-unit-hadoop-hdfs-project_hadoop-hdfs-rbf.txt](https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2887/1/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs-rbf.txt)
| hadoop-hdfs-rbf in the patch passed. |
| +1 :green_heart: | asflicense | 0m 30s | | The patch does not
generate ASF License warnings. |
| | | 94m 43s | | |
| Reason | Tests |
|---:|:--|
| Failed junit tests |
hadoop.hdfs.server.federation.router.TestRouterRpcMultiDestination |
| | hadoop.hdfs.server.federation.router.TestRouterRpc |
| | hadoop.hdfs.server.federation.router.TestRouterAllResolver |
| Subsystem | Report/Notes |
|--:|:-|
| Docker | ClientAPI=1.41 ServerAPI=1.41 base:
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2887/1/artifact/out/Dockerfile
|
| GITHUB PR | https://github.com/apache/hadoop/pull/2887 |
| Optional Tests | dupname asflicense compile javac javadoc mvninstall
mvnsite unit shadedclient spotbugs checkstyle codespell |
| uname | Linux ed950788e3c0 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28
05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | dev-support/bin/hadoop.sh |
| git revision | trunk / ed8da9f7a95c79e9c7c06aebca255a55aeb95244 |
| Default Java | Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08 |
| Multi-JDK versions |
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04
[jira] [Work logged] (HDFS-15960) Router NamenodeHeartbeatService fails to authenticate with namenode in a kerberized envi
[ https://issues.apache.org/jira/browse/HDFS-15960?focusedWorklogId=580117=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-580117 ] ASF GitHub Bot logged work on HDFS-15960: - Author: ASF GitHub Bot Created on: 09/Apr/21 16:21 Start Date: 09/Apr/21 16:21 Worklog Time Spent: 10m Work Description: bolerio opened a new pull request #2887: URL: https://github.com/apache/hadoop/pull/2887 -- 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: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 580117) Remaining Estimate: 0h Time Spent: 10m > Router NamenodeHeartbeatService fails to authenticate with namenode in a > kerberized envi > > > Key: HDFS-15960 > URL: https://issues.apache.org/jira/browse/HDFS-15960 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Borislav Iordanov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > We use http.hadoop.authentication.type = "kerberos" and when the > NamenodeHeartbeatService calls the namenode via JMX, it is not providing a > user security context so the authentication token is not transmitted and it > fails. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
