[
https://issues.apache.org/jira/browse/HADOOP-19419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shilun Fan resolved HADOOP-19419.
-
Fix Version/s: 3.5.0
Hadoop Flags: Reviewed
Target Version/s: 3.5.0
Res
[
https://issues.apache.org/jira/browse/HADOOP-19423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shilun Fan resolved HADOOP-19423.
-
Fix Version/s: 3.5.0
Hadoop Flags: Reviewed
Target Version/s: 3.5.0
Res
[
https://issues.apache.org/jira/browse/HADOOP-19427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shilun Fan resolved HADOOP-19427.
-
Fix Version/s: 3.5.0
Hadoop Flags: Reviewed
Target Version/s: 3.5.0
Res
[
https://issues.apache.org/jira/browse/HADOOP-19430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shilun Fan resolved HADOOP-19430.
-
Fix Version/s: 3.5.0
Hadoop Flags: Reviewed
Target Version/s: 3.5.0
Res
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java11-linux-x86_64/851/
[Apr 22, 2025, 9:50:15 AM] (github) Revert "YARN-11765. Refactor: Move Clock
Class from hadoop-mapreduce-project to hadoop-common-project for Reusability
(#7352) Contributed by Jiandan Yang." (#759
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1920/
[Apr 22, 2025, 9:50:15 AM] (github) Revert "YARN-11765. Refactor: Move Clock
Class from hadoop-mapreduce-project to hadoop-common-project for Reusability
(#7352) Contributed by Jiandan Yang." (#759
[
https://issues.apache.org/jira/browse/HADOOP-19418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shilun Fan resolved HADOOP-19418.
-
Fix Version/s: 3.5.0
Hadoop Flags: Reviewed
Target Version/s: 3.5.0
Res
@Xiaoqiao He Thanks very much for responsing.
1. Yes, this proposal is related to RBF and ARR features.
2. Usually, slow nameservices will not affect the performance of other normal
nameservices due to the async handler thread pool. But there exists an
extremely rare situation that retry invo
+ hdfs-dev.
Thanks Haobo for your proposal. As you mentioned above, this may be
related to RBF and ARR features, right?
IMO, it is necessary to improve responder performance, but I am a
little confused about nameservice will slow
down the whole system, The first glance is client or package size
sh
PJ Fanning created HADOOP-19552:
---
Summary: upgrade jsonschema2pojo due to CVE-2025-3588
Key: HADOOP-19552
URL: https://issues.apache.org/jira/browse/HADOOP-19552
Project: Hadoop Common
Issue Ty
[
https://issues.apache.org/jira/browse/HADOOP-19412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shilun Fan resolved HADOOP-19412.
-
Fix Version/s: 3.5.0
Hadoop Flags: Reviewed
Target Version/s: 3.5.0
Res
[
https://issues.apache.org/jira/browse/HADOOP-19411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shilun Fan resolved HADOOP-19411.
-
Fix Version/s: 3.5.0
Hadoop Flags: Reviewed
Target Version/s: 3.5.0
Res
think you meant to send this to hdfs-dev, not the -subscribe list.
On Wed, 16 Apr 2025 at 14:09, Zhanghaobo wrote:
> Hello, everyone, so sorry to bother you and I would like to discuss how
> to optimize the invoke retry logic of async repsonder when some
> nameservices are slow.
> Currently,
I like it, even if gcs want to be more agile at first
1. can help testing/debugging against a broadly used store
2. stops us accidentally breaking things (who would do that 🙂)
3. makes it easier to do changes across the modules
Because Chris is involved, I'm not worried about this being
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1735/
No changes
-1 overall
The following subsystems voted -1:
asflicense hadolint mvnsite pathlen unit
The following subsystems voted -1 but
were configured to be filtered/ignored:
cc
15 matches
Mail list logo
