[jira] [Created] (HADOOP-19155) Fix TestZKSignerSecretProvider failing unit test
kuper created HADOOP-19155:
--
Summary: Fix TestZKSignerSecretProvider failing unit test
Key: HADOOP-19155
URL: https://issues.apache.org/jira/browse/HADOOP-19155
Project: Hadoop Common
Issue Type: Test
Components: auth
Affects Versions: 3.4.0
Reporter: kuper
Attachments: 企业微信截图_4436de68-18c5-43bf-9382-4d9a853f7ef0.png,
企业微信截图_ab901a4a-c0d4-4a20-a595-057cf648c30c.png,
企业微信截图_fa5e7d54-b3a8-4ca3-8d4a-25fe493b4eb1.png
* {{TestZKSignerSecretProvider and
}}{{{}TestRandomSignerSecretProvider{}}}}} unit test o{}}}ccasional failure
* The reason was that the MockZKSignerSecretProvider class rollSecret method
is {{synchronized}}
* {{{}s{}}}ometimes verify (secretProvider, timeout (timeout). AtLeastOnce
()). RollSecret () method first in RolloverSignerSecretProvider scheduler
thread lock, this results in a timeout
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-18937) Add journalnode maintenance node list
[ https://issues.apache.org/jira/browse/HADOOP-18937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] kuper resolved HADOOP-18937. Resolution: Abandoned > Add journalnode maintenance node list > - > > Key: HADOOP-18937 > URL: https://issues.apache.org/jira/browse/HADOOP-18937 > Project: Hadoop Common > Issue Type: Improvement > Components: fs >Affects Versions: 3.3.6 >Reporter: kuper >Priority: Trivial > > * In the case of configuring 3 journal nodes in HDFS, if only 2 journal nodes > are available and 1 journal node fails to start due to machine issues, it > will result in a long initialization time for the namenode (around 30-40 > minutes, depending on the IPC timeout and retry policy configuration). > * The failed journal node cannot recover immediately, but HDFS can still > function in this situation. In our production environment, we encountered > this issue and had to reduce the IPC timeout and adjust the retry policy to > accelerate the namenode initialization and provide services. > * I'm wondering if it would be possible to have a journal node maintenance > list to speed up the namenode initialization knowing that one journal node > cannot provide services in advance? -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-18937) Add journalnode maintenance node list
kuper created HADOOP-18937: -- Summary: Add journalnode maintenance node list Key: HADOOP-18937 URL: https://issues.apache.org/jira/browse/HADOOP-18937 Project: Hadoop Common Issue Type: Improvement Components: fs Affects Versions: 3.3.6 Reporter: kuper * In the case of configuring 3 journal nodes in HDFS, if only 2 journal nodes are available and 1 journal node fails to start due to machine issues, it will result in a long initialization time for the namenode (around 30-40 minutes, depending on the IPC timeout and retry policy configuration). * The failed journal node cannot recover immediately, but HDFS can still function in this situation. In our production environment, we encountered this issue and had to reduce the IPC timeout and adjust the retry policy to accelerate the namenode initialization and provide services. * I'm wondering if it would be possible to have a journal node maintenance list to speed up the namenode initialization knowing that one journal node cannot provide services in advance? -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-18864) Multiple token access is supported in HA noZK KMS environment
kuper created HADOOP-18864: -- Summary: Multiple token access is supported in HA noZK KMS environment Key: HADOOP-18864 URL: https://issues.apache.org/jira/browse/HADOOP-18864 Project: Hadoop Common Issue Type: Improvement Components: kms Affects Versions: 3.3.6 Reporter: kuper Attachments: image-2023-08-24-19-53-24-665.png When there is no configuration of ZooKeeper synchronization for secrets on the KMS server (hadoop.kms.authentication.signer.secret.provider is null), the YARN MapReduce job fails to run successfully. The reason is that the KMS returns an error "invalidToken" as it cannot find the corresponding token in the cache. !image-2023-08-24-19-53-24-665.png! -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-18817) Exclude aws-java-sdk-swf-libraries packages to avoid compilation failures
kuper created HADOOP-18817:
--
Summary: Exclude aws-java-sdk-swf-libraries packages to avoid
compilation failures
Key: HADOOP-18817
URL: https://issues.apache.org/jira/browse/HADOOP-18817
Project: Hadoop Common
Issue Type: Bug
Components: build
Affects Versions: 3.3.6
Reporter: kuper
The compilation failed when I packaged through the maven command
{code:java}
mvn clean install -DskipTests -Dtar -Pdist -Pnative {code}
report an error:
{code:java}
[WARNING]
Dependency convergence error for
com.amazonaws:aws-java-sdk-simpleworkflow:1.12.367 paths to dependency are:
+-org.apache.hadoop:hadoop-aws:3.3.6
+-com.amazonaws:aws-java-sdk-bundle:1.12.367
+-com.amazonaws:aws-java-sdk:1.12.367
+-com.amazonaws:aws-java-sdk-simpleworkflow:1.12.367
and
+-org.apache.hadoop:hadoop-aws:3.3.6
+-com.amazonaws:aws-java-sdk-bundle:1.12.367
+-com.amazonaws:aws-java-sdk:1.12.367
+-com.amazonaws:aws-java-sdk-swf-libraries:1.11.22
+-com.amazonaws:aws-java-sdk-simpleworkflow:1.11.22
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence
failed with message:
Failed while enforcing releasability. See above detailed error message. {code}
com.amazonaws:aws-java-sdk-swf-libraries are not required
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
