text:
Early stop on failed start (Alternative to #13087)

Fixes issues with tasks running for a long time despite a failed start

Description

The following log appeared during initialization of a peon but the task kept running without making any progress.
2022-09-08T17:01:20,448 ERROR [main-EventThread] org.apache.druid.curator.CuratorModule - Unhandled error in Curator, stopping server.
java.lang.NullPointerException: null
	at org.apache.curator.framework.imps.EnsembleTracker.configToConnectionString(EnsembleTracker.java:185) ~[curator-framework-4.3.0.jar:4.3.0]
	at org.apache.curator.framework.imps.EnsembleTracker.processConfigData(EnsembleTracker.java:206) ~[curator-framework-4.3.0.jar:4.3.0]
	at org.apache.curator.framework.imps.EnsembleTracker.access$300(EnsembleTracker.java:50) ~[curator-framework-4.3.0.jar:4.3.0]
	at org.apache.curator.framework.imps.EnsembleTracker$2.processResult(EnsembleTracker.java:150) ~[curator-framework-4.3.0.jar:4.3.0]
	at org.apache.curator.framework.imps.CuratorFrameworkImpl.sendToBackgroundCallback(CuratorFrameworkImpl.java:883) [curator-framework-4.3.0.jar:4.3.0]
	at org.apache.curator.framework.imps.CuratorFrameworkImpl.processBackgroundOperation(CuratorFrameworkImpl.java:653) [curator-framework-4.3.0.jar:4.3.0]
	at org.apache.curator.framework.imps.WatcherRemovalFacade.processBackgroundOperation(WatcherRemovalFacade.java:152) [curator-framework-4.3.0.jar:4.3.0]
	at org.apache.curator.framework.imps.GetConfigBuilderImpl$2.processResult(GetConfigBuilderImpl.java:222) [curator-framework-4.3.0.jar:4.3.0]
	at org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:598) [zookeeper-3.5.9.jar:3.5.9]
	at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:510) [zookeeper-3.5.9.jar:3.5.9]

This patch attempts to halt instead of exit in such cases.

This PR has:

[ ] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[ ] a release note entry in the PR description.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[ ] been tested in a test Druid cluster.

I don't believe that this will actually solve the problem.  The exception that happened was causing the shutdown hooks to not make progress, IIRC.  The docs suggest that halt will also run the shutdown hooks, unless they have already been triggered.  But, this is the code that's responsible for triggering them, the change in this PR is effectively no change.

Okay, I think I read the .halt javadoc wrong...  So, yeah, ignore that previous comment.
The real comment is this: what happens if we never get to the finally block?  Like, if we block forever on that lifecycle.stop().  I forget the status of the threads when we ran into this, but I want to remember that it never even got to the System.exit() call.  What if we skip the lifecycle.stop entirely and just halt?

Merging since build failure is due to an unrelated flaky IT

authors: AmatyaAvadhanula imply-cheddar


text:
Add snakeyaml dependency back in

Description
While doing some testing on my other PR (https://github.com/apache/druid/pull/14030) with the new fabric8 library version, I noticed some snakeyaml error when starting up the overlord. We need to add the snakeyaml library into the pom still as fabric8 6.4.1 still depends on it
This PR has:

[X ] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[ ] a release note entry in the PR description.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[X ] been tested in a test Druid cluster.

the dependency checker part of ci seems to be complaining that this dependency is not used, should we just ignore it?
[INFO] --- maven-dependency-plugin:3.1.1:analyze (default-cli) @ druid-kubernetes-overlord-extensions ---
Warning:  Unused declared dependencies found:
Warning:     org.yaml:snakeyaml:jar:1.33:compile

the dependency checker part of ci seems to be complaining that this dependency is not used, should we just ignore it?

[INFO] --- maven-dependency-plugin:3.1.1:analyze (default-cli) @ druid-kubernetes-overlord-extensions ---

Warning:  Unused declared dependencies found:

Warning:     org.yaml:snakeyaml:jar:1.33:compile

let me check if updating the version will help, i can see what version of snakeyaml fabric8 uses exactly

Let's hold off on this change.  The reason to put it in was so that the snakeyaml dependency would be included in the bundle.  Adding this into the pom does not seem to fix that.

source: gharchive/pull-request

authors: clintropolis georgew5656 nlippis

repo: apache/druid

license_type: permissive

license_source: github-api


text:
Dubbo GSoC 2023 - Pure Dubbo RPC API

At present, Dubbo provides RPC capabilities and a large number of service governance capabilities. This has led to the fact that Dubbo cannot be used well if some of Dubbo's own components only need to use RPC capabilities or some users who need extreme lightweight.
Goal: To provide a Dubbo RPC kernel, users can directly program for service calls and focus on RPC.
https://issues.apache.org/jira/browse/DUBBO-118

I'm working on it.

I am very interested in this task, and I will submit a proposal for this task in the future.

source: gharchive/issue

repo: apache/dubbo


text:
org.apache.dubbo.registry.integration.RegistryDirectory疑似内存泄漏

Environment
Dubbo version: 2.7.12
Java version: 1.8
Steps to reproduce this issue
1.网关系统
2.通过泛化调用后台业务系统
问题
1、系统有FullGC告警，dump内存分析内存泄漏问题：发现有1万多个org.apache.dubbo.registry.integration.RegistryDirectory这个实例
2、分析是ConsumerConfigurationListener.listeners这个List数组持有的对象，通过分析对象发现这些有很多serviceKey(对应的是接口的类名全路径)重复的对象，其中url中的host有不同的值，ZK-1、ZK-2、ZK-3正好我们有3台zk集群，但是其他的重复发现每种不同的zk有20个重复对象，看不出里面的区别

上图只是其中一个接口，每个接口的个数还不一样，不清楚这里的具体逻辑

问题已找到：
1、我们有调用ReferenceConfig.destroy()

问题已找到： 1、我们有调用ReferenceConfig.destroy() 3295 也是同样的问题，但是他在2.7.1修复了，我使用的版本是2.7.12还是有这个问题

升级到2.7.15

谢谢，忘记关闭了，我在 #9558 中已经关闭了该问题


text:
[DUBBO-4405]: instread of throwing exception, print warninig message for now

What is the purpose of the change
fix #4405
Brief changelog
XXXXX
Verifying this change
XXXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #5011 into master will increase coverage by 0.09%.
The diff coverage is 0%.

@@             Coverage Diff             @@
##             master   #5011      +/-   ##
===========================================
+ Coverage      63.9%     64%   +0.09%
  Complexity      451     451
===========================================
  Files           769     769
  Lines         33171   33171
  Branches       5231    5231
===========================================
+ Hits          21198   21231      +33
+ Misses         9552    9515      -37
- Partials       2421    2425       +4

Impacted Files
Coverage Δ
Complexity Δ

...org/apache/dubbo/config/context/ConfigManager.java
66.66% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ng/exchange/support/header/HeartbeatTimerTask.java
73.68% <0%> (-5.27%)
0% <0%> (ø)

...ava/org/apache/dubbo/common/utils/ConfigUtils.java
80% <0%> (-0.75%)
0% <0%> (ø)

...g/apache/dubbo/registry/consul/ConsulRegistry.java
62.5% <0%> (+0.62%)
29% <0%> (ø)
:arrow_down:

.../exchange/support/header/HeaderExchangeServer.java
66.98% <0%> (+1.88%)
0% <0%> (ø)
:arrow_down:

.../dubbo/remoting/transport/netty4/NettyChannel.java
64.77% <0%> (+2.27%)
0% <0%> (ø)
:arrow_down:

.../rpc/protocol/dubbo/LazyConnectExchangeClient.java
58.82% <0%> (+2.35%)
0% <0%> (ø)
:arrow_down:

...exchange/support/header/HeaderExchangeHandler.java
67.21% <0%> (+2.45%)
0% <0%> (ø)
:arrow_down:

...pache/dubbo/registry/support/AbstractRegistry.java
81.6% <0%> (+3.06%)
0% <0%> (ø)
:arrow_down:

...c/main/java/org/apache/dubbo/rpc/RpcException.java
83.33% <0%> (+3.33%)
0% <0%> (ø)
:arrow_down:

... and 5 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 597cda8...a406c73. Read the comment docs.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.beiwei.ly seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Fixed in master.

authors: CLAassistant beiwei30 chickenlj codecov-io


text:
perf: Improve the performance for generating random numbers

What is the purpose of the change
see #8166
Brief changelog
Update Random to ThreadLocalRandom
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[x] GitHub Actions works fine on your own branch.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #8167 (c0f0312) into 3.0 (532ce72) will decrease coverage by 0.15%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##                3.0    #8167      +/-   ##
============================================
- Coverage     61.87%   61.71%   -0.16%
  Complexity      313      313
============================================
  Files          1074     1074
  Lines         45167    45165       -2
  Branches       6791     6791
============================================
- Hits          27945    27873      -72
- Misses        14156    14211      +55
- Partials       3066     3081      +15

Impacted Files
Coverage Δ

.../rpc/cluster/router/mesh/route/MeshRuleRouter.java
84.96% <100.00%> (-0.20%)
:arrow_down:

...ng/transport/dispatcher/all/AllChannelHandler.java
68.96% <0.00%> (-20.69%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
46.15% <0.00%> (-15.39%)
:arrow_down:

...ng/transport/dispatcher/WrappedChannelHandler.java
47.82% <0.00%> (-15.22%)
:arrow_down:

.../remoting/transport/netty4/NettyClientHandler.java
57.62% <0.00%> (-10.17%)
:arrow_down:

.../apache/dubbo/remoting/transport/AbstractPeer.java
63.04% <0.00%> (-6.53%)
:arrow_down:

.../remoting/transport/netty4/NettyServerHandler.java
56.81% <0.00%> (-4.55%)
:arrow_down:

...ubbo/rpc/protocol/dubbo/ChannelWrappedInvoker.java
43.47% <0.00%> (-4.35%)
:arrow_down:

...ubbo/common/url/component/param/DynamicValues.java
79.16% <0.00%> (-4.17%)
:arrow_down:

...ava/org/apache/dubbo/config/DubboShutdownHook.java
83.33% <0.00%> (-3.34%)
:arrow_down:

... and 17 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 532ce72...c0f0312. Read the comment docs.

authors: codecov-commenter pinxiong


text:
[Enhancement] Implement methods from storage-plugin.admin rocketmq

从EM的storage.admin中实现方法 并尝试做一些拓展，方便后续对其他指标进行监控

[X] Yes I am willing to submit a PR

Completed in https://github.com/apache/eventmesh-dashboard/pull/66

repo: apache/eventmesh-dashboard


text:
[Enhancement] Code reuse is extracted as a method.[SendMessageRequestProtocolResolver]

Search before asking

[X] I had searched in the issues and found no similar issues.

Enhancement Request

located at:
eventmesh-protocol-plugin/eventmesh-protocol-meshmessage/src/main/java/org/apache/eventmesh/protocol/meshmessage/resolver/http/SendMessageRequestProtocolResolver.java line 67-98,101-132
Describe the solution you'd like

Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

hey @Alonexc I would like to like to work on this. Can you please explain more about the issue?

@monish-byte Of course, you are very welcome to pr.

authors: Alonexc monish-byte

repo: apache/eventmesh


text:
[FLINK-28300] Fix helm lint invalid Yaml document separator

Fixes FLINK-28300

Thank you @MaksimAniskov , next time when you open a PR please tag both the PR and the commit with the jira like : [FLINK-XXXX] My Commit/PR message this way it's easier for reviewers.
you can find details about the process for more complex changes here: https://flink.apache.org/contributing/contribute-code.html

@morhidi will fix the typo and merge tomorrow, thanks for the ping

authors: MaksimAniskov gyfora mbalassi

repo: apache/flink-kubernetes-operator


text:
[hotfix][docs] Typo fix in doc pages

What is the purpose of the change

Remove the extra space separator.

Brief change log

I have modified some files in the docs/content/docs directory.

Verifying this change

I checked the changes.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changes to the CustomResourceDescriptors: (no)
Core observer or reconciler logic that is regularly executed: (no)

Documentation

Does this pull request introduce a new feature? (no)

can you please run the maven build locally before submitting any more fixes? This puts really unnecessary strain on the CI system.

there should not be any more changed files after running
mvn clean install -Pgenerate-docs

@gyfora I ran the maven build locally before committing.


text:
[FLINK-21920] Optimize DefaultScheduler#allocateSlots

What is the purpose of the change
Based on the scheduler benchmark introduced in FLINK-21731, we find that there are two procedures related to DefaultScheduler#allocateSlots have O(N^2) complexity:

ExecutionSlotSharingGroupBuilder#tryFindAvailableProducerExecutionSlotSharingGroupFor
ExecutionGraphToInputsLocationsRetrieverAdapter#getConsumedResultPartitionsProducers

Based on FLINK-21326, we can replace the usages of consumed partitions with ConsumedPartitionGroup and optimize the complexity from O(N^2) to O(N).
Brief change log

Optimize ExecutionSlotSharingGroupBuilder#tryFindAvailableProducerExecutionSlotSharingGroupFor
Optimize ExecutionGraphToInputsLocationsRetrieverAdapter#getConsumedResultPartitionsProducers

Verifying this change
Since these optimizations don't change the original logic of related procedures, we believe these changes should be covered by existing test cases, such as ExecutionGraphToInputsLocationsRetrieverAdapterTest, LocalInputPreferredSlotSharingStrategyTest, and etc.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@Thesharing Could you share the number of the improvements with this change?
If there is not too much improvement, I tend to not do this improvement because it changed the previous stateless ExecutionGraphToInputsLocationsRetrieverAdapter into a stateful one, which may make it harder to achieve a scalable graph in the future.

The proposed solution will make ExecutionGraphToInputsLocationsRetrieverAdapter stateful, which is hard to maintain. However, the improvement of this optimization seems not obvious. For now we just close it. If later we got a better idea, we'd like to reopen it.

authors: Thesharing zhuzhurk

repo: apache/flink


text:
[release-1.13][FLINK-24010][connector/common] HybridSourceReader/Enumerator delegate checkpoint notifications

Cherry pick of https://github.com/apache/flink/pull/17006

@flinkbot run azure


text:
[FLINK-24280] Support manual checkpoints triggering from a MiniCluster

What is the purpose of the change
We want to have a way to trigger a checkpoint at a well defined point in time. The feature is intended to be used purely in tests and benchmarks
Brief change log

3ac77bd - changes the MockSourceReader so that it can wait for the initial splits. Without the change it could've finished before any splits were assigned to it, even though there were AddSplitsEvent(s) "on the wire"
e7af45a - exposes an already available method CheckpointCoordinator#triggerCheckpoint(boolean periodic) through REST APIs of (Dispatcher/JobManager/...)

Verifying this change
Added tests in ManualCheckpointITCase
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@flinkbot run azure

LGTM % one comment

authors: dawidwys pnowojski


text:
[FLINK-27155][changelog] Reduce multiple reads to the same Changelog …

…file in the same taskmanager during restore
What is the purpose of the change
Reduce multiple reads to the same changelog file in the same taskmanager during restare, described in FLINK-27155.
Brief change log

extract file open from StateChangeFormat to StateChangeIteratorImpl and StateChangeIteratorWithCache
add StateChangeIteratorWithCache for cache dstl file to local
make FsStateChangelogStorageForRecovery use StateChangeIteratorWithCache for create StateChangelogHandleReader

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: yes
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no

@flinkbot run azure

Thanks a lot for your advice @rkhachatryan , I feel like I can learn a lot from it. Since there are still some personal matters this week, I will be considering your suggestions one by one next week. Thanks again !

Hi @zoltar9264, would you like to continue this work? It would be great to have it in Flink 1.16.
The feature freeze for 1.16 is scheduled for Aug 9, so there's not much time left.
If you have other items, I or my colleauges could work on it if you don't mind.

Hi @rkhachatryan , sorry for the delay in this pr due to my busy work for the past two weeks, I will do it as soon as possible .

@flinkbot run azure

Hi @rkhachatryan , I found that it is possible to verify that cache is working properly in ChangelogRescalingITCase, how do you think about ?

Hi @zoltar9264, do you mean modifying somehow the existing test? I think it should be fine.

Hi @rkhachatryan , I have modified ChangelogRescalingITCase to cover ChangelogStreamHandleReaderWithCache.

Thanks @rkhachatryan !
I'm very grateful for your help over the past few weeks, I've learned a lot in it, and I'm sorry for the trouble I've caused you due to my inexperience.

Thank you for the contribution @zoltar9264, great work!
Glad to hear that and no worries :)


text:
[FLINK-25909][runtime][security] Add HBaseDelegationTokenProvider

What is the purpose of the change
Basically this is a revamp of #20206 (seems like it's discontinued) with minor modifications and additional testing so copy-pasting the description.
This PR adds HBaseDelegationTokenProvider to obtain HBase delegation tokens using the new delegation token framework.
Brief change log

Add HBaseDelegationTokenProvider
Add HBaseDelegationTokenProvider into the META-INFO service registration

Verifying this change
This provider functionality will be covered by some existing tests. But We don't have dedicated tests to test the HBase delegation token obtaining. I think we may need to add new end-to-end tests to cover it.
Manually tests on Yarn, detailed: Test Gist
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? All documentation is intended to be added in FLINK-25911 when everything works as a whole

The tests failed w/ the following issue:
2022-10-24T15:02:28.1434134Z ERROR: Could not find a version that satisfies the requirement pemja==0.2.6 (from apache-flink) (from versions: none)

Rebasing to the latest master.

I don't see any fix so just restarting it first.

@flinkbot run azure

Thanks for the explanation @gaborgsomogyi, I plan to verify based on the linked instructions.

Sorry for the delay, but finally I was able to spend some time on this and verified that the token obtain logic works as expected:
2022-11-03 11:37:08,236 INFO  org.apache.flink.runtime.security.token.HBaseDelegationTokenProvider [] - Obtaining Kerberos security token for HBase
...
2022-11-03 11:37:09,460 INFO  org.apache.flink.runtime.security.token.HBaseDelegationTokenProvider [] - Added HBase Kerberos security token to credentials.

I was running the app on YARN with an HBase 2.4.6 server on the Cloudera stack.
PR itself LGTM.

authors: ferenc-csaky gaborgsomogyi


text:
[FLINK-24998] Update CI image

switch to Temurin JDK 11 (latest)
update Temurin JDK 17 to latest

JDK 17 update is the important bit, fixing the observed SIGSEGV.

Test failure is unrelated; see FLINK-32291.

You can look at the commits in https://github.com/zentol/flink-ci-docker/commits/master.
The last 4 commits are relevant for this upgrade.
You can also check the layers in https://hub.docker.com/layers/chesnay/flink-ci/java_8_11_17_maven_386_v2/images/sha256-566fc00ee070850d47dc082e50bcdfbc7a07cea5b7bd3bc08c3943eba1cc9e4b?context=repo.

I understand that it means a bit of overhead for minor changes like that one.

I think it's a bit more of a hindrance than you think.

(e.g. apache/flink-docker?)

It doesn't belong in flink-docker imo; should be a separate repo.
(Ideally flink-docker is mostly merged into the flink repo eventually, only serving as a publishing area for official-images.)

(having explicit versions in the code that enable us to actual review such a change)

I don't think the reviewability is impacted by this being in my own repo :thinking:

couldn't we use the Flink Docker registry for the CI Docker image as well

We could, but then I have to ping someone else for making any change to the image because we don't have enough seats in the apache org. GHCR + GHA would make more sense, but we'd have to invest some time into setting things up.
That being said, it's a reasonable idea, so feel free to file tickets to that end.

You can look at the commits in https://github.com/zentol/flink-ci-docker/commits/master.
The last 4 commits are relevant for this upgrade.

Thanks for the reference: That helps in understanding this change :+1:

I don't think the reviewability is impacted by this being in my own repo thinking

You're right - the remark on using your repository isn't related to improving the reviewability. That one was more of a organizational/political remark.

You can also check the layers in https://hub.docker.com/layers/chesnay/flink-ci/java_8_11_17_maven_386_v2/images/sha256-566fc00ee070850d47dc082e50bcdfbc7a07cea5b7bd3bc08c3943eba1cc9e4b?context=repo.

That's actually a good hint - I wasn't aware of that. Thanks

It doesn't belong in flink-docker imo; should be a separate repo.
(Ideally flink-docker is mostly merged into the flink repo eventually, only serving as a publishing area for official-images.)

I just noticed that your repo is just a fork of flink-ci/flink-ci-docker which sounds more appropriate but isn't because it's under Ververica, instead :man_shrugging:

authors: XComp zentol


text:
[FLINK-32373][sql-client] Support passing headers with SQL Client gateway requests

What is the purpose of the change
FLINK-32030 and FLINK-32035 enable communication from the SQL Client to the SQL Gateway placed behind a proxy (i.e. a K8S ingress). Such use cases typically require authentication. This PR enables authentication by adding the ability to supply custom headers to the underlying RestClient.
Verifying this change

Added a test that verifies that custom headers are read and parsed correctly

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
A follow up docs PR will be created to document URLs support in SQL Client gateway mode, including the custom headers feature

@flinkbot run azure

@flinkbot run azure

Flaky test failure. Passed in a private pipeline https://dev.azure.com/alexanderfedulov/Flink/_build/results?buildId=484&view=results

@flinkbot run azure

@flinkbot run azure


text:
[FLINK-33778][table] Cleanup usage of deprecated TableConfig#setIdleS…

What is the purpose of the change
Replace the usage of deprecated org.apache.flink.table.api.TableConfig#setIdleStateRetentionTime(Time, Time)
with setIdleStateRetentionTime(Duration)
Brief change log

Cleanup usage of deprecated TableConfig#setIdleStateRetentionTime(Time, Time) *

Verifying this change

original unit test *

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no )
The runtime per-record code paths (performance sensitive): (no )
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)

hi @snuyanzin @dawidwys  could you help review this pr?

hi @lsyldliu @xuyangzhong  will you also help review this?

@xuyangzhong thanks for your review and fix the description of pr

LTGM. BTW, should we also update this function in pyflink? cc @HuangXingBo Further more, please modify the description of this pr.

the python code of  has no use, we do not need modify
def set_idle_state_retention_time(self,
                                  min_time: datetime.timedelta,
                                  max_time: datetime.timedelta):


text:
[hotfix][docs] fix typo in classloading option in Debugging Classloading

https://issues.apache.org/jira/browse/FLINK-33997
Closed for duplicates.
https://github.com/apache/flink/pull/24052


text:
[FLINK-4218] [checkpoints] Do not rely on FileSystem to determine state sizes

This prevents failures on eventually consistent S3, where the operations for keys (=entries in the parent directory/bucket) are not guaranteed to be immediately consistent (visible) after a blob was written.
Not relying on any operation on keys (= requesting FileStatus) should mitigate the problem.
This also changes the exception signature from getStateSize() from Exception to IOException, which fits more natural with the exception signatures of some other I/O methods.
Related issue: We may still want to have retries on FileStatus operations on S3, for other parts of the system (like FileOutputFormats)

@StefanRRichter Maybe interesting for you to review.

Manually merged in 95e9004e36fffae755eab7aa3d5d0d5e8bfb7113


text:
[FLINK-5006] SystemProcessingTimeServiceTest.testTimerSorting fails

Hello!
I'v reproduced this issue on my environment several times.
I found that the test uses ScheduledThreadPoolExecutor  as threadFactory (actually SystemProcessingTimeService uses). ScheduledThreadPoolExecutor does not guarantee that tasks will be executed immediately after delay:

Delayed tasks execute no sooner than they are enabled, but without any real-time guarantees about when, after they are enabled, they will commence.

See Oracle docs
Thus, order of executions and adding timestamps to ArrayBlockingQueue isn't defined. So it looks like the test is not correct.
In changes I increased intervals between tasks, it helps to avoid falling.
If I am correct, maybe it makes sense to get rid of this test?

I guess the problem is that when the tasks get registered at the ScheduledThreadPoolExecutor, multiple tasks may have a delay of zero, which makes the order of triggering undefined.
What do you think?

Yes it is. The ThreadPoolExecutor is not claiming to be a real-time system with any sort of timing guarantees.
The only thing it will guarantee is that it doesn't run tasks too early.

It's not about timing guarantees here, only about order of running timers.
The problem is that they are sorted by the delay which is affected by races/stalls, rather than by proper timestamp.
Since Flink actually relies on timer triggering order, I think we need to implement our own timer service, which sorts by actual timestamp, rather than by delay.

@StephanEwen I think it's not a problem that these physical, low-level timers don't fire in order of their timestamp because the ordering of timers is maintained in the implementation of InternalTimerService (in a queue in the current implementation). Also, under normal circumstances we only have one active timer at the ProcessingTimeService (SystemProcessingTimeService).

@aljoscha Okay, if that is the only thing that we use it for, then order is indeed not important for that service. Are we sure it is not used in other places?

@StephanEwen It's used to drive the automatic watermark generation and the inactivity timer in the BucketingSink, but those are cases where the order doesn't matter.

Okay, if that is the case, then we should probably simply remove the "test timer sorting" test and note down that this does not give any guarantees on the order of timers.
@BorisOsipov What do you think about this?

@aljoscha thank you for additional research and comments.
@StephanEwen I think we can remove it as I proposed earlier.
I'v removed test and added javadoc to registerTimer method. Please look at this.
Is it ok?

Looks good, merging this!
Thanks, @BorisOsipov for bearing with us on this one through the long discussion!

authors: BorisOsipov StephanEwen aljoscha


text:
[FLINK-5542] use YarnCluster vcores setting to do MaxVCore validation

What is the purpose of the change
See. FLINK-5542
use YarnCluster vcores setting to do MaxVCore validation instead of using the local yarn conf.
Brief change log

Fetch MaxVCore num via yarnClient instead of using the local yarn conf

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
But I already reproduced the Error/Exception, after the fix, it's working as expected.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not documented)

cc @rehevkor5 @tillrohrmann

Thanks for your review. @tillrohrmann
Resolved your comment. Looking forward for further work at FLINK community. About the proposal you mentioned on having a exhaustive check on job submission, I will try go through more submit scenarios and see if what we can do to achieve the exhaustive check goal and create a new follow up issue, thanks.

Hi, I am taking a look again.

@GJL resolved yours comments.

LGTM, merging as soon as build is green.

@GJL Kindly remind. Build is ready to go.

authors: GJL leanken


text:
[FLINK-12508] Expand Testing Documentation

What is the purpose of the change
Expand the documentation on testing DataStream API pipelines
Brief change log

extend section on unit testing Flink operators
add documentation about MiniClusterWithClientResource

Verifying this change

build docs and proofread

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving):  no
The serializers:  no
The runtime per-record code paths (performance sensitive):  no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper:  no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

@sjwiesman Thank you for the review and your valuable suggestions. I have updated the branch accordingly.

@flinkbot approve description

authors: knaufk rmetzger


text:
set timeout on FluoAdminIT

This is a test.  Travis seems to keep timing out on FluoAdminImplIT.  Set timeouts on that test to see what happens.

I actually wanted this build to fail.  I have run it twice so far and the test has not timed out.  Maybe the third time will be the charm.

Fixed by #959

repo: apache/fluo


text:
GEODE-5635: Fix running http tests in IntelliJ

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to dev@geode.apache.org.

The geode-core jar is not being pulled in by IJ for either integration or distributed tests. This ends up doing that. I would have expected just integrationTestRuntime project(':geode-core') to work, but it doesn't.

So geode-core has some crazy rules in it still for producing multiple artifacts. It’s possible that IJ is looking for something that is a result of on of those other artifacts. It’s not included in the main jar but some other jar. Let’s identify what classes it is so we can fix the generation and dependency of that artifact.

Waiting for IntelliJ 2018.3

authors: jdeppe-pivotal pivotal-jbarrett

repo: apache/geode


text:
GEODE-6728: Generify ClusterManagementService.list

Co-authored-by: Owen Nichols onichols@pivotal.io
Co-authored-by: Jens Deppe jdeppe@pivotal.io
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to dev@geode.apache.org.

@Petahhh

With this, the compiler is still happy when we do this
RegionConfig regionConfig = new RegionConfig();
List<MemberConfig> result = service.list(regionConfig, MemberConfig.class).getResult();

We can avoid overly "genetify" the interface simply by adding a getResult(Class) method in ClusterManagementResult:
  public <R extends RuntimeCacheElement> List<R> getResult(Class<R> clazz) {
    return result.stream().map(clazz::cast).collect(Collectors.toList());
  }

Just for comparison: https://github.com/apache/geode/pull/3532/files

authors: jdeppe-pivotal jinmeiliao


text:
HDDS-2610. Fix the ObjectStore#listVolumes failure when argument is null

What changes were proposed in this pull request?
Fix the OmMetadataManagerImpl#listVolumes to list all volumes when the userName is null.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-2610
How was this patch tested?
UT Updating, and build & run on cluster.

Thanks @bharatviswa504 for the review.
Fix in progress, hope soon.

Update listAllvolumes with parameter prefix and startKey for complete utility.

Hi @cxorm , looks like Attila has already approved these changes. Can you please rebase the patch, we can help commit it once rebased.

The pr-check / unit (pull_request)  seems not related to the patch.

/retest

Thank you @arp7 for looking this PR.
The error check is not related to the patch.
Here is the same branch passed all checks.

Filed HDDS-3151 for the integration test failure, which we've seen earlier without this change, too.
Acceptance test failure that SCM does not come out of safe mode is also observed elsewhere.
Given we have a clean run on the PR source branch, and it's only 2 commits behind master, I think it's safe to merge.
Thanks @cxorm for the contribution, @bharatviswa504 and @arp7 for the review.

Thanks all for the help.

authors: adoroszlai arp7 cxorm

repo: apache/hadoop-ozone


text:
HADOOP-18154. S3A Authentication to support WebIdentity

Description of PR
The PR addresses a requirement to comply with AWS security concept IAM roles for service accounts (IRSA) while operating a service that isn't based on Apache Spark and that runs inside Amazon Elastic Kubernetes Service (EKS).
The code change consists in adding a new credentials provider class org.apache.hadoop.fs.s3a.OIDCTokenCredentialsProvider to the module hadoop-aws.
How was this patch tested?
No new unit-test or integration-test was created on-purpose. The patch was "only" tested based on Hadoop release 2.10.1, as part of our specific use-case based on Delta sharing service v0.4.0 along with the following Hadoop configuration (core-site.xml):
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="configuration.xsl"?>
<configuration>
  <property>
    <name>fs.s3a.aws.credentials.provider</name>
    <value>org.apache.hadoop.fs.s3a.OIDCTokenCredentialsProvider</value>
  </property>
  <property>
    <name>fs.s3a.jwt.path</name>
    <value>/var/run/secrets/eks.amazonaws.com/serviceaccount/token</value>
  </property>
  <property>
    <name>fs.s3a.assumed.role.arn</name>
    <value>my_iam_role_arn</value>
  </property>
  <property>
    <name>fs.s3a.assumed.role.session.name</name>
    <value>my_iam_session_name</value>
  </property>
  <property>
      <name>fs.s3a.server-side-encryption-algorithm</name>
      <value>SSE-KMS</value>
  </property>
  <property>
      <name>fs.s3a.server-side-encryption.key</name>
      <value>my_kms_key_id</value>
  </property>
</configuration>

For code changes:

[X] The title or this PR starts with the corresponding JIRA issue 'HADOOP-18154'
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[X] No new dependency was added to the code.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 56s

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
36m 28s

trunk passed

+1 :green_heart:
compile
0m 43s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
0m 36s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 24s

trunk passed

+1 :green_heart:
mvnsite
0m 41s

trunk passed

+1 :green_heart:
javadoc
0m 22s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 30s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m  4s

trunk passed

+1 :green_heart:
shadedclient
23m 54s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 32s

the patch passed

+1 :green_heart:
compile
0m 35s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
0m 35s

the patch passed

+1 :green_heart:
compile
0m 29s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 29s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 18s
/results-checkstyle-hadoop-tools_hadoop-aws.txt
hadoop-tools/hadoop-aws: The patch generated 36 new + 0 unchanged - 0 fixed = 36 total (was 0)

+1 :green_heart:
mvnsite
0m 35s

the patch passed

+1 :green_heart:
javadoc
0m 16s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 23s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m  7s

the patch passed

+1 :green_heart:
shadedclient
23m 11s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 33s

hadoop-aws in the patch passed.

-1 :x:
asflicense
0m 29s
/results-asflicense.txt
The patch generated 1 ASF License warnings.

96m 43s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4070/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4070

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux 5e56e3e68c47 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / d213b2ce9833bb7e482fbdebc76259713334c70f

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4070/1/testReport/

Max. process+thread count
521 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4070/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m 29s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

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
38m  6s

trunk passed

+1 :green_heart:
compile
0m 49s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
0m 41s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 26s

trunk passed

+1 :green_heart:
mvnsite
0m 47s

trunk passed

+1 :green_heart:
javadoc
0m 23s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 32s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 19s

trunk passed

+1 :green_heart:
shadedclient
24m 12s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 36s

the patch passed

+1 :green_heart:
compile
0m 42s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
0m 42s

the patch passed

+1 :green_heart:
compile
0m 32s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 32s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 19s
/results-checkstyle-hadoop-tools_hadoop-aws.txt
hadoop-tools/hadoop-aws: The patch generated 21 new + 0 unchanged - 0 fixed = 21 total (was 0)

+1 :green_heart:
mvnsite
0m 39s

the patch passed

+1 :green_heart:
javadoc
0m 16s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 27s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 19s

the patch passed

+1 :green_heart:
shadedclient
23m 22s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 41s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
0m 31s

The patch does not generate ASF License warnings.

100m 34s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4070/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4070

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux fb302480fe5f 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / f7207421d305b78d47f0b48ab3656b4bede78ac7

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4070/2/testReport/

Max. process+thread count
525 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4070/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  3s

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
37m 39s

trunk passed

+1 :green_heart:
compile
0m 48s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
0m 39s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 26s

trunk passed

+1 :green_heart:
mvnsite
0m 47s

trunk passed

+1 :green_heart:
javadoc
0m 23s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 33s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 16s

trunk passed

+1 :green_heart:
shadedclient
24m 12s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 38s

the patch passed

+1 :green_heart:
compile
0m 43s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
0m 43s

the patch passed

+1 :green_heart:
compile
0m 33s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 33s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 19s
/results-checkstyle-hadoop-tools_hadoop-aws.txt
hadoop-tools/hadoop-aws: The patch generated 21 new + 0 unchanged - 0 fixed = 21 total (was 0)

+1 :green_heart:
mvnsite
0m 39s

the patch passed

+1 :green_heart:
javadoc
0m 16s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 26s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 21s

the patch passed

+1 :green_heart:
shadedclient
23m 46s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 48s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
0m 30s

The patch does not generate ASF License warnings.

100m  7s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4070/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4070

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux f4fb3cfaeef7 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / f7207421d305b78d47f0b48ab3656b4bede78ac7

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4070/3/testReport/

Max. process+thread count
521 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4070/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 59s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

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
37m  1s

trunk passed

+1 :green_heart:
compile
0m 43s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
0m 35s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 25s

trunk passed

+1 :green_heart:
mvnsite
0m 43s

trunk passed

+1 :green_heart:
javadoc
0m 23s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 30s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 18s

trunk passed

+1 :green_heart:
shadedclient
24m 20s

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 38s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
0m 38s

the patch passed

+1 :green_heart:
compile
0m 30s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 30s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 18s
/results-checkstyle-hadoop-tools_hadoop-aws.txt
hadoop-tools/hadoop-aws: The patch generated 21 new + 0 unchanged - 0 fixed = 21 total (was 0)

+1 :green_heart:
mvnsite
0m 34s

the patch passed

+1 :green_heart:
javadoc
0m 16s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 25s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m 11s

the patch passed

+1 :green_heart:
shadedclient
23m 48s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 31s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
0m 30s

The patch does not generate ASF License warnings.

98m 40s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4070/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4070

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux 12f0006b81cf 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / e624ea1a7cc9224ac2f23ed69506711b9f52bb88

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4070/5/testReport/

Max. process+thread count
521 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4070/5/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 53s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

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
36m 59s

trunk passed

+1 :green_heart:
compile
0m 42s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
0m 35s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 24s

trunk passed

+1 :green_heart:
mvnsite
0m 41s

trunk passed

+1 :green_heart:
javadoc
0m 22s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 29s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m  5s

trunk passed

+1 :green_heart:
shadedclient
23m 18s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 32s

the patch passed

+1 :green_heart:
compile
0m 35s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
0m 35s

the patch passed

+1 :green_heart:
compile
0m 29s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 29s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 17s
/results-checkstyle-hadoop-tools_hadoop-aws.txt
hadoop-tools/hadoop-aws: The patch generated 13 new + 0 unchanged - 0 fixed = 13 total (was 0)

+1 :green_heart:
mvnsite
0m 34s

the patch passed

+1 :green_heart:
javadoc
0m 15s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 24s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
1m  6s

the patch passed

+1 :green_heart:
shadedclient
23m 11s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m 29s

hadoop-aws in the patch passed.

+1 :green_heart:
asflicense
0m 29s

The patch does not generate ASF License warnings.

96m 34s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4070/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4070

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux 7947a5edc92d 4.15.0-153-generic #160-Ubuntu SMP Thu Jul 29 06:54:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 93773618af72386ae99d37540557715cd46ba160

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4070/6/testReport/

Max. process+thread count
571 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4070/6/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

so as well as authing with a webidentidy token, we could use https://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRoleWithWebIdentity.html  to get role credentials for up to 12h. which could go into a delegation token.

@mehakmeet

we need this feature, can somebody please help?

Hey @steveloughran. Could you please provide status update on this PR, so you plan to merge it, or it's already outdated?

@jclarysse - I am looking for this same capability - we're deploying trino / hive metastore (on top of Hadoop) in EKS, and of course service account -> iam role mappings do not work as is.
Is this PR merged anyplace where we can build and try out inside of hive metastore?
Thanks.

Trunk is on aws v2 sdk now; it's where features go in. once something is in there a patch for branch-3.3 may be considered; that'd have to be a v1 implementation of the same feature so I'd be reluctant to add it as it would be very different.

Anyone who wants this: please carry on with the PR against hadoop trunk. this may mean restarting from scratch with the v2 sdk -but do reference this PR in the description @jclarysse  deserves credit in the commit comments too

authors: boblozano hadoop-yetus insider89 jclarysse steveloughran vikaskoppineedi

repo: apache/hadoop


text:
HBASE-23909 : list_regions raise correct error if it is being splitte…

…d/merged/transitioning

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 20s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
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.

_ master Compile Tests _

+1 :green_heart:
mvninstall
6m  7s
master passed

+1 :green_heart:
javadoc
0m 14s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 43s
the patch passed

+1 :green_heart:
rubocop
0m  4s
There were no new rubocop issues.

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
javadoc
0m 12s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
7m  2s
hbase-shell in the patch passed.

+1 :green_heart:
asflicense
0m 13s
The patch does not generate ASF License warnings.

22m  7s

Subsystem
Report/Notes

Docker
Client=19.03.7 Server=19.03.7 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1238/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1238

Optional Tests
dupname asflicense javac javadoc unit rubocop

uname
Linux 3eec8647ff74 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1238/out/precommit/personality/provided.sh

git revision
master / 9bd39786df

Default Java
1.8.0_181

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1238/1/testReport/

Max. process+thread count
3437 (vs. ulimit of 10000)

modules
C: hbase-shell U: hbase-shell

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1238/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) rubocop=0.80.1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

authors: Apache-HBase virajjasani

repo: apache/hbase


text:
HBASE-24205 Create metric to know the number of reads that happens fr…

…om memstore (#1929)

HBASE-24205 - Create metric to know the number of reads that happens (#1920)

HBASE-24205 - Create metric to know the number of reads that happens
from memstore (branch-2)

Add the optimization as in master and fix whitestyle and checkstyle

Fix compilation error that accidently crept in

Authored-by: Ramkrishna ramkrishna@apache.org
Signed-off by:Anoop Sam Johnanoopsamjohn@gmail.com
Signed-off by:Viraj Jasanivirajjasani@apache.org

Merger changes

Remove unnecessary methods as part of rebase

Removed the empty lines

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 21s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2.3 Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 47s
branch-2.3 passed

+1 :green_heart:
checkstyle
1m 38s
branch-2.3 passed

+1 :green_heart:
spotbugs
2m 54s
branch-2.3 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 38s
the patch passed

-0 :warning:
checkstyle
1m 15s
hbase-server: The patch generated 1 new + 37 unchanged - 1 fixed = 38 total (was 38)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
18m 32s
Patch does not cause any errors with Hadoop 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
3m 24s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 32s
The patch does not generate ASF License warnings.

46m  4s

Subsystem
Report/Notes

Docker
Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1958/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1958

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 0f3b73ff9013 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.3 / 666fd1d11f

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1958/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

Max. process+thread count
84 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1958/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 45s
Docker mode activated.

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.3 Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 26s
branch-2.3 passed

+1 :green_heart:
compile
1m 46s
branch-2.3 passed

+1 :green_heart:
shadedjars
5m 59s
branch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 21s
hbase-hadoop2-compat in branch-2.3 failed.

-0 :warning:
javadoc
0m 16s
hbase-hadoop-compat in branch-2.3 failed.

-0 :warning:
javadoc
0m 39s
hbase-server in branch-2.3 failed.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 20s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m  1s
the patch passed

+1 :green_heart:
compile
1m 44s
the patch passed

+1 :green_heart:
javac
1m 44s
the patch passed

+1 :green_heart:
shadedjars
6m 41s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 20s
hbase-hadoop-compat in the patch failed.

-0 :warning:
javadoc
0m 21s
hbase-hadoop2-compat in the patch failed.

-0 :warning:
javadoc
0m 49s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
0m 32s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
0m 38s
hbase-hadoop2-compat in the patch passed.

+1 :green_heart:
unit
140m 21s
hbase-server in the patch passed.

172m 45s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1958/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1958

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux b21eb8bf3c28 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.3 / 666fd1d11f

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1958/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-hadoop2-compat.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1958/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-hadoop-compat.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1958/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1958/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-hadoop-compat.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1958/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-hadoop2-compat.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1958/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1958/1/testReport/

Max. process+thread count
4355 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1958/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 44s
Docker mode activated.

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.3 Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 40s
branch-2.3 passed

+1 :green_heart:
compile
1m 31s
branch-2.3 passed

+1 :green_heart:
shadedjars
5m  3s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  7s
branch-2.3 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 25s
the patch passed

+1 :green_heart:
compile
1m 25s
the patch passed

+1 :green_heart:
javac
1m 25s
the patch passed

+1 :green_heart:
shadedjars
5m  3s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  5s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 25s
hbase-hadoop-compat in the patch passed.

+1 :green_heart:
unit
0m 27s
hbase-hadoop2-compat in the patch passed.

+1 :green_heart:
unit
151m 47s
hbase-server in the patch passed.

178m 54s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1958/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1958

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 5d29cf5494e0 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.3 / 666fd1d11f

Default Java
1.8.0_232

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1958/1/testReport/

Max. process+thread count
3497 (vs. ulimit of 12500)

modules
C: hbase-hadoop-compat hbase-hadoop2-compat hbase-server U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1958/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.