text:
[BEAM-8654] Fixes resolutionStrategy's interference with dependency check

The weekly Jenkins job beam_Dependency_Check does not receive the latest version information from Gradle-version-plugin. The job has been interfered by resolutionStrategy in BeamModulePlugin.groovy (detail: BEAM-8654 and https://github.com/ben-manes/gradle-versions-plugin/issues/361).

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---

---
---

Java

Python

---

---
---

XLang
---
---
---

---
---
---

Pre-Commit Tests Status (on master branch)

---
Java
Python
Go
Website

Non-portable

Portable
---

---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

Run Seed Job

Run CommunityMetrics PreCommit

Run Java PreCommit

Run Python PreCommit

Run Java PreCommit

Run Dependency Check

R: @yifanzou
It successfully created https://issues.apache.org/jira/projects/BEAM/issues/BEAM-8691 for bigtable-client-core (and many other JIRA tickets 8674 - 8728)
Although somehow the email "Beam Dependency Check Report (2019-11-15)" still missing the artifact, submitting this PR as a small incremental change.

Run Java PreCommit

Run Python2_PVR_Flink PreCommit
Run Python PreCommit

Run Python PreCommit

Run Python2_PVR_Flink PreCommit

Run Dependency Check

Run Python PreCommit

@yifanzou (All checks have passed now; I see you're a committer) Would you merge this?


text:
[BEAM-9980] tests tied with Python versions configurable

Made it possible for some tests to configure which python version to use  with gradle properties

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
Post-Commit Tests Status (on master branch)

Lang
SDK
Dataflow
Flink
Samza
Spark
Twister2

Go

---

---

---

Java

Python

---

---

XLang
---
---

---

---

Pre-Commit Tests Status (on master branch)

---
Java
Python
Go
Website

Non-portable

Portable
---

---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

R: @tvalentyn

thanks a lot for this work, @lazylynx. Sorry for taking too long to respond, will try to take a look tomorrow.

Thank you for review @tvalentyn !
I prefer to split to separated commits, I will update and resolve conflicts later.
And thank you for suggestion for introducing the concept of high/low priority versions.
I do agree your plan.

@tvalentyn Thank you for detail comments.
I made codes to just refactor current tests. PTAL.

@tvalentyn updated. PTAL.

Thanks, @lazylynx . The change LGTM, will run some tests to make sure things didn't break.

Run Python MongoDBIO_IT

Run Python 3.5 PostCommit

Run Python 3.6 PostCommit

Run Chicago Taxi on Dataflow

Run Python MongoDBIO_IT

Run Python 2 PostCommit

@tvalentyn OK, I will split this PR to be separated by test-suites.
And this PR will be updated to one for dataflow test-suite.

Run Chicago Taxi on Dataflow

Run Python MongoDBIO_IT

Run Python MongoDBIO Load Test

Run PythonDocker PreCommit

Run PythonDocker PreCommit

MongoDB failure is unrelated, opened https://issues.apache.org/jira/browse/BEAM-10718.

source: gharchive/pull-request

authors: lazylynx tvalentyn

repo: apache/beam

license_type: permissive

license_source: github-api


text:
[BEAM-10956] Adds duration string to the ib.show and ib.collect

Change-Id: I29df95dc29c67116d7bc81ee999173b5c932afb8
Adds a duration string to ib.show and ib.collect. This still allows for integer seconds and "inf".

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
Post-Commit Tests Status (on master branch)

Lang
SDK
Dataflow
Flink
Samza
Spark
Twister2

Go

---

---

---

Java

Python

---

---

XLang

---

---

---

Pre-Commit Tests Status (on master branch)

---
Java
Python
Go
Website
Whitespace
Typescript

Non-portable

Portable
---

---
---
---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @pabloem

R: @KevinGG


text:
[BEAM-10029] Adds Grafana config for Spanner IO Perf Metrics

Updated Python_IO_IT_Tests_Dataflow.json file and adds config for spanner io perf (read and write) metrics into it.
I haven't found a way to test the grafana and this config locally but hoping this configuration is all it requires to update the beam metrics. Please let me know if there anything needs to be added.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
ValidatesRunner compliance status (on master branch)

Lang
ULR
Dataflow
Flink
Samza
Spark
Twister2

Go
---

---

---

Java

Python
---

---

---

XLang

---

---

Examples testing status on various runners

Lang
ULR
Dataflow
Flink
Samza
Spark
Twister2

Go
---
---
---
---
---
---
---

Java
---

---
---
---
---
---

Python
---
---
---
---
---
---
---

XLang
---
---
---
---
---
---
---

Post-Commit SDK/Transform Integration Tests Status (on master branch)

Go
Java
Python

Pre-Commit Tests Status (on master branch)

---
Java
Python
Go
Website
Whitespace
Typescript

Non-portable

Portable
---

---
---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @aaltay
Would you please review or add a reviewer? Thanks!

See (https://cwiki.apache.org/confluence/display/BEAM/Community+Metrics) for updating deploying changes to metrics system. If that works, this PR is probably good to be merged. (It is hard to review a json file that we unfortunately have tests for.)
/cc @tysonjh @alanmyrvold - Are there best practices for reviewing changes to metrics dashboard?

Thanks, @aaltay for the Wiki links. I've tested it locally and made few adjustments. Here's the screenshot for ref.

authors: aaltay mszb


text:
[BEAM-13009] Bugfix: Prevent dataloss in DynamoDBIO write if deduplication keys are not set (aws SDK v1)

This is porting the fix in https://github.com/apache/beam/pull/15895 back onto the aws module for sdk v1.
https://github.com/apache/beam/pull/12583 introduced a mechanism to deduplicate elements per batch based on deduplication keys. Unfortunately the mechanism is not backwards compatible. If upgrading without setting the deduplication keys all elements end up with the same empty deduplication key. As a result only one element per batch is ever written to DynamoDB, everything else is lost.
This change makes sure elements are deduplicated based on element equality if no deduplication keys are provided.
Missing unit tests for reads and writes are added to better catch such bugs in the future.
Bugs in DynamoDBIOTest (using localstack) are fixed, further improvements of this (proper integration testing) should be done in BEAM-7559.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
ValidatesRunner compliance status (on master branch)

Lang
ULR
Dataflow
Flink
Samza
Spark
Twister2

Go
---

---

Java

Python
---

---

XLang

---

Examples testing status on various runners

Lang
ULR
Dataflow
Flink
Samza
Spark
Twister2

Go
---
---
---
---
---
---
---

Java
---

---
---
---
---
---

Python
---
---
---
---
---
---
---

XLang
---
---
---
---
---
---
---

Post-Commit SDK/Transform Integration Tests Status (on master branch)

Go
Java
Python

Pre-Commit Tests Status (on master branch)

---
Java
Python
Go
Website
Whitespace
Typescript

Non-portable

Portable
---

---
---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @aromanenko-dev
R: @iemejia

Run Java_Examples_Dataflow_Java11 PreCommit

R: @dennisylyung


text:
[BEAM-13115][Playground] Security – Mock Storage

Added mock storage via volume isolation with tmpfs for Beam Playground Backend.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
ValidatesRunner compliance status (on master branch)

Lang
ULR
Dataflow
Flink
Samza
Spark
Twister2

Go
---

---

Java

Python
---

---

XLang

---

Examples testing status on various runners

Lang
ULR
Dataflow
Flink
Samza
Spark
Twister2

Go
---
---
---
---
---
---
---

Java
---

---
---
---
---
---

Python
---
---
---
---
---
---
---

XLang
---
---
---
---
---
---
---

Post-Commit SDK/Transform Integration Tests Status (on master branch)

Go
Java
Python

Pre-Commit Tests Status (on master branch)

---
Java
Python
Go
Website
Whitespace
Typescript

Non-portable

Portable
---

---
---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @tvalentyn


text:
Making the default BigQuery write disposition to be WRITE_APPEND

The current default write disposition behavior is WRITE_EMPTY, so in order to write to a non-empty table, a write dispostion parameter has to be manually configured. Defaulting it to WRITE_APPEND can rule out this issue.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

r: @pabloem @manavgarg

b/268111530

lgtm thanks!


text:
Move code contribution guide into repo

This should hopefully make things more discoverable

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @liferoad


text:
Fix interactive tests for Beam Notebooks release

Specific fixes are as follows:

Update chromedriver to 117
Update golden screenshots
Enforce urllib3 <2.x.x

Tested this with the following:
cd sdks/python
python setup.py bdist_wheel --universal
pip install --upgrade -e '.[interactive_test,test,interactive]'
pytest -rsx -v apache_beam/runners/interactive/testing/integration/tests

This fails before the changes and succeeds after.
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @liferoad


text:
Fix BigtableConfigTranslator

If timeouts are set on BigtableIO directly, it should always override the configuration set in BigtableOptions.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

assign set of reviewers

GCP IO Direct PreCommit testHL7v2IO_ListHL7v2Messages known flaky test not related

authors: Abacn mutianf


text:
Various smaller-scale changes extracted while working on SDF

Extracted out of PR https://github.com/apache/beam/pull/5566/
One minor change per commit.
R: @bsidhom
CC: @lukecwik

CC: @youngoli since you were planning to work on adding state/timers to ULR - the GBK and watermark code changes will be relevant to you.

Fixed the two test errors; the third one in testGBK seems to be a flake (a problem for sure, but not caused by this PR)

The flake is https://issues.apache.org/jira/browse/BEAM-4473

Added a fix for that issue. 100 runs of ReferenceRunner.pipelineExecution pass now.

Seems the java precommit failed due to a Jenkins infra failure, after having successfully executed everything else. This is ready for review, but I'm going to restart the tests too.

retest this please

Rebased.

(test failure in Elasticsearch seems unrelated - I'll look into it but this is ready for review nevertheless)

retest this please


text:
[BEAM-6243] Add an experiment to use Python's optimizer on Flink.

I've successfully run 1GB-sized TFT jobs locally with this change.

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

R: @angoenka
You only need to look a the last commit, the previous two are currently pending review but I will rebase as they get merged into master.


text:
[BEAM-7501] 2.7.1 LTS backport: fixes concatenated compressed files bug with python sdk

This cherrypicks #8187 and #8784 to 2.7.1 LTS release

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---

---
---

Java

Python

---

---
---

Pre-Commit Tests Status (on master branch)

---
Java
Python
Go
Website

Non-portable

Portable
---

---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

@dlesco FYI in case you are interested

LGTM. Thanks.

All test suites that exist for 2.7 are healthy. Merging.

authors: chamikaramj kennknowles


text:
Support bthread rwlock

What problem does this PR solve?
Issue Number:
Problem Summary:
What is changed and the side effects?
Changed:

按照golang读写锁原理，在bRPC实现了对应的读写锁。
支持bthread信号量，用于满足读写锁的实现需求，同时可以开放给用户使用。
contention profiler支持bthread信号量和读写锁。

Side effects:

Performance effects(性能影响):

Breaking backward compatibility(向后兼容性):

Check List:

Please make sure your changes are compilable(请确保你的更改可以通过编译).
When providing us with a new feature, it is best to add related tests(如果你向我们增加一个新的功能, 请添加相关测试).
Please follow Contributor Covenant Code of Conduct.(请遵循贡献者准则).

请问这个PR什么时候可以合入呢？ 对rwlock有需求，之前提个PR被反馈性能不好，希望尽快用上官方的实现

请问这个PR什么时候可以合入呢？ 对rwlock有需求，之前提个PR被反馈性能不好，希望尽快用上官方的实现

没那么快。读写锁的核心功能已经实现了，还有一些需要优化的地方。

@wwbmmm 再看看。整理了一下commit，分成三部分，review起来清晰一点。

LGTM

请问这个PR什么时候可以合入呢？ 对rwlock有需求，之前提个PR被反馈性能不好，希望尽快用上官方的实现

@ketor 读写锁的PR已经合入了。之前用#2748 的UT对比了一下两个实现的性能，本PR的性能比#2748 要好一些。

authors: chenBright ketor wwbmmm

repo: apache/brpc


text:
Buildstream should identify if an element moves from build-depend to depend, and not recompile.

See original issue on GitLab
In GitLab by [Gitlab user @tcanabrava] on Oct 13, 2020, 15:22
when we have a library that is incorrectly configured, and we need to move an element from build-depend to depend there is no need to recompile.
If this library is down on the stack, it get's worse as everything that depends on it will also be recompiled, but the result library is the same.

In GitLab by [Gitlab user @tristanvb] on Oct 13, 2020, 15:36
Seems like this should produce the same cache key for the element itself, but not for any reverse dependencies which have a build dependency on the element which changed.

When you move a dependency from build-depends to depends, you are making a statement that this dependency is required at runtime.
A reverse dependency which build depends on this element, requires this element to run at the time the reverse dependency builds, thus, the new runtime dependency is necessarily a new build time dependency for any reverse build dependencies.

Is this essentially the behavior you are observing ? Or is the element itself also rebuilt as a result of this, not only its reverse dependencies ?

In GitLab by [Gitlab user @tcanabrava] on Oct 13, 2020, 18:46
you are completely right, I misunderstood the issue.

source: gharchive/issue

repo: apache/buildstream


text:
Automatically make generate every night

We can run a new task into the changelog workflow (and name it differently) to run a make generate every night and include any change in API, doc, whatever is regenerated automatically to avoid forgetting stuff or writing code that will be cleaned eventually.
Ref #3818 #3867

Also let's not forget to run make build in the same workflow and update pkg/resources/resources.go nightly.

Also let's not forget to run make build in the same workflow and update pkg/resources/resources.go nightly.

Thinking more carefully, do you think the resources.go should be at all something to refresh in the repo? after all, this is always regenerated, I'd be even inclined to git ignore it in order to reduce any possibility of conflict. However, I am not 100% sure of what could be a best practice with this kind of golang resource.

authors: squakez tadayosi

repo: apache/camel-k


text:
CAMEL-12575:NPE on GET request with Content-Type header

CAMEL-12575:NPE on GET request with Content-Type header

And maybe it would be good to use ObjectHelper too to check for null

repo: apache/camel


text:
[HOTFIX] Modified code to fix the degrade in compaction performance

Problem
Compaction performance for 3.5 billion degraded by 16-20%
Analysis:
Code modification in RawResultIerator.java has caused the problem wherein few extra checks are performed as compared to previous code
Fix
Revert the changes in RawResultIerator class

[ ] Any interfaces changed?
No
[ ] Any backward compatibility impacted?
NA
[ ] Document update required?
No
[ ] Testing done
Verified in cluster testing
[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.
NA

SDV Build Success , Please check CI http://144.76.159.231:8080/job/ApacheSDVTests/6184/

Build Failed  with Spark 2.1.0, Please check CI http://136.243.101.176:8080/job/ApacheCarbonPRBuilder1/7807/

Build Failed with Spark 2.2.1, Please check CI http://88.99.58.216:8080/job/ApacheCarbonPRBuilder/6531/

SDV Build Success , Please check CI http://144.76.159.231:8080/job/ApacheSDVTests/6189/

SDV Build Success , Please check CI http://144.76.159.231:8080/job/ApacheSDVTests/6191/

Build Failed  with Spark 2.1.0, Please check CI http://136.243.101.176:8080/job/ApacheCarbonPRBuilder1/7815/

Build Failed with Spark 2.2.1, Please check CI http://88.99.58.216:8080/job/ApacheCarbonPRBuilder/6539/

SDV Build Success , Please check CI http://144.76.159.231:8080/job/ApacheSDVTests/6196/

Build Failed with Spark 2.2.1, Please check CI http://88.99.58.216:8080/job/ApacheCarbonPRBuilder/6546/

Build Failed  with Spark 2.1.0, Please check CI http://136.243.101.176:8080/job/ApacheCarbonPRBuilder1/7822/

SDV Build Success , Please check CI http://144.76.159.231:8080/job/ApacheSDVTests/6201/

Build Success with Spark 2.1.0, Please check CI http://136.243.101.176:8080/job/ApacheCarbonPRBuilder1/7827/

Build Success with Spark 2.2.1, Please check CI http://88.99.58.216:8080/job/ApacheCarbonPRBuilder/6553/

LGTM

authors: CarbonDataQA manishgupta88 ravipesala

repo: apache/carbondata


text:
[Presto][Streaming] support presto read streaming table

Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[ ] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Success with Spark 2.1.0, Please check CI http://136.243.101.176:8080/job/ApacheCarbonPRBuilder2.1/1844/

Build Success with Spark 2.2.1, Please check CI http://95.216.28.178:8080/job/ApacheCarbonPRBuilder1/2052/

Build Success with Spark 2.1.0, Please check CI http://136.243.101.176:8080/job/ApacheCarbonPRBuilder2.1/1866/

Build Success with Spark 2.3.2, Please check CI http://136.243.101.176:8080/job/carbondataprbuilder2.3/10121/

Build Success with Spark 2.2.1, Please check CI http://95.216.28.178:8080/job/ApacheCarbonPRBuilder1/2074/

Build Success with Spark 2.1.0, Please check CI http://136.243.101.176:8080/job/ApacheCarbonPRBuilder2.1/1870/

Build Failed with Spark 2.2.1, Please check CI http://95.216.28.178:8080/job/ApacheCarbonPRBuilder1/2079/

Build Failed  with Spark 2.3.2, Please check CI http://136.243.101.176:8080/job/carbondataprbuilder2.3/10125/

@QiangCai Can you explain the dependency of readers after this PR? Ideally, presto module should depends on streaming reader in core or hadoop modules.

Build Success with Spark 2.1.0, Please check CI http://136.243.101.176:8080/job/ApacheCarbonPRBuilder2.1/1962/

Build Failed  with Spark 2.3.2, Please check CI http://136.243.101.176:8080/job/carbondataprbuilder2.3/10214/

Build Failed with Spark 2.2.1, Please check CI http://95.216.28.178:8080/job/ApacheCarbonPRBuilder1/2235/

Build Success with Spark 2.1.0, Please check CI http://136.243.101.176:8080/job/ApacheCarbonPRBuilder2.1/2118/

Build Success with Spark 2.2.1, Please check CI http://95.216.28.178:8080/job/ApacheCarbonPRBuilder1/2324/

Build Success with Spark 2.3.2, Please check CI http://136.243.101.176:8080/job/carbondataprbuilder2.3/10373/

Build Success with Spark 2.1.0, Please check CI http://136.243.101.176:8080/job/ApacheCarbonPRBuilder2.1/2170/

Build Success with Spark 2.3.2, Please check CI http://136.243.101.176:8080/job/carbondataprbuilder2.3/10425/

Build Success with Spark 2.2.1, Please check CI http://95.216.28.178:8080/job/ApacheCarbonPRBuilder1/2385/

authors: CarbonDataQA QiangCai jackylk


text:
CASSANDRA-15928 Throw FSWriteError upon write failures in order to apply DiskFailureP…

…olicy

@yifan-c would you mind to close this PR if it is not relevant anymore as it was already merged?

authors: smiklosovic yifan-c

repo: apache/cassandra


text:
Unable to add ESXi Host

ISSUE TYPE

Bug Report

COMPONENT NAME
Management server
CLOUDSTACK VERSION
4.15.0
CONFIGURATION
N/A
OS / ENVIRONMENT
Management server

Ubuntu 20.04

Hypervisor

vCenter 6.7
ESXI 6.7

SUMMARY
When I tried to add an ESXi host, I got an error message "Error 530 Unable to add host" and could not add the host.
This is a screenshot of the error.

In the "ESX/ESXi Host" field, I put the FQDN of my ESXi host.
I have also registered to vCenter with that FQDN.
Also, the zone's internal DNS server can resolve both forward and reverse DNS lookups.
STEPS TO REPRODUCE

Create Zone.
Try to add ESXi host.

EXPECTED RESULTS
ESXi hosts can be added without error.
ACTUAL RESULTS
"Error 530 Unable to add Host" is displayed and ESXi host cannot be added.
This is Error log(/var/log
2021-05-06 00:43:50,808 INFO  [c.c.r.ResourceManagerImpl] (qtp1644231115-16:ctx-9d55a0d4 ctx-5805610d) (logid:bda73b7f) Trying to add a new host at http://<my-vCenter-fqdn>/home-dc1/cloud-cluster/<my-esxi-hostfqdn> in data center 1
2021-05-06 00:43:50,808 INFO  [c.c.h.v.VmwareServerDiscoverer] (qtp1644231115-16:ctx-9d55a0d4 ctx-5805610d) (logid:bda73b7f) Discover host. dc: 1, pod: 1, cluster: 2, uri host: <my-vCenter-fqdn>
2021-05-06 00:43:51,179 INFO  [c.c.h.v.VmwareServerDiscoverer] (qtp1644231115-16:ctx-9d55a0d4 ctx-5805610d) (logid:bda73b7f) Detected private network label : vSwitch0
2021-05-06 00:43:51,179 DEBUG [c.c.h.v.r.VmwareContextFactory] (qtp1644231115-16:ctx-9d55a0d4 ctx-5805610d) (logid:bda73b7f) initialize VmwareContext. url: https://<my-vCenter-fqdn>/sdk/vimService, username: administrator@vsphere.local, password: 4********
2021-05-06 00:43:51,384 INFO  [c.c.h.v.u.VmwareContext] (qtp1644231115-16:ctx-9d55a0d4 ctx-5805610d) (logid:bda73b7f) New VmwareContext object, current outstanding count: 2
2021-05-06 00:43:51,408 ERROR [c.c.h.v.u.VmwareContext] (qtp1644231115-16:ctx-9d55a0d4 ctx-5805610d) (logid:bda73b7f) Path element points to an un-existing inventory entity
2021-05-06 00:43:51,409 ERROR [c.c.h.v.m.VmwareManagerImpl] (qtp1644231115-16:ctx-9d55a0d4 ctx-5805610d) (logid:bda73b7f) Unable to find host from inventory path: /home-dc1/cloud-cluster/<my-esxi-hostfqdn>
2021-05-06 00:43:51,409 INFO  [c.c.h.v.VmwareServerDiscoverer] (qtp1644231115-16:ctx-9d55a0d4 ctx-5805610d) (logid:bda73b7f) Found 0 hosts.
2021-05-06 00:43:51,409 ERROR [c.c.h.v.VmwareServerDiscoverer] (qtp1644231115-16:ctx-9d55a0d4 ctx-5805610d) (logid:bda73b7f) Unable to find host or cluster based on url: /home-dc1/cloud-cluster/<my-esxi-hostfqdn>
2021-05-06 00:43:51,410 INFO  [c.c.h.v.u.VmwareContext] (qtp1644231115-16:ctx-9d55a0d4 ctx-5805610d) (logid:bda73b7f) Disconnecting VMware session
2021-05-06 00:43:51,415 WARN  [c.c.r.ResourceManagerImpl] (qtp1644231115-16:ctx-9d55a0d4 ctx-5805610d) (logid:bda73b7f) Unable to find the server resources at http://<my-vCenter-fqdn>/home-dc1/cloud-cluster/<my-esxi-hostfqdn>
2021-05-06 00:43:51,415 INFO  [c.c.u.e.CSExceptionErrorCode] (qtp1644231115-16:ctx-9d55a0d4 ctx-5805610d) (logid:bda73b7f) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions
2021-05-06 00:43:51,416 WARN  [o.a.c.a.c.a.h.AddHostCmd] (qtp1644231115-16:ctx-9d55a0d4 ctx-5805610d) (logid:bda73b7f) Exception:
com.cloud.exception.DiscoveryException: Unable to add the host
        at com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:826)
        at com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:612)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
        at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:95)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212)
        at com.sun.proxy.$Proxy188.discoverHosts(Unknown Source)
        at org.apache.cloudstack.api.command.admin.host.AddHostCmd.execute(AddHostCmd.java:142)
        at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:156)
        at com.cloud.api.ApiServer.queueCommand(ApiServer.java:764)
        at com.cloud.api.ApiServer.handleRequest(ApiServer.java:588)
        at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:321)
        at com.cloud.api.ApiServlet$1.run(ApiServlet.java:134)
        at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
        at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
        at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
        at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:131)
        at com.cloud.api.ApiServlet.doPost(ApiServlet.java:98)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:665)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:750)
        at org.eclipse.jetty.servlet.ServletHolder$NotAsyncServlet.service(ServletHolder.java:1386)
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:547)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
        at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:590)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
        at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235)
        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1610)
        at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1300)
        at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:485)
        at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1580)
        at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1215)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
        at org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:767)
        at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
        at org.eclipse.jetty.server.Server.handle(Server.java:500)
        at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:383)
        at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:547)
        at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:375)
        at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:273)
        at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
        at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
        at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336)
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313)
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171)
        at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129)
        at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:375)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:806)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:938)
        at java.base/java.lang.Thread.run(Thread.java:829)
2021-05-06 00:43:51,421 INFO  [c.c.a.ApiServer] (qtp1644231115-16:ctx-9d55a0d4 ctx-5805610d) (logid:bda73b7f) Unable to add the host
2021-05-06 00:43:51,422 DEBUG [c.c.a.ApiServlet] (qtp1644231115-16:ctx-9d55a0d4 ctx-5805610d) (logid:bda73b7f) ===END===  10.41.7.133 -- POST  command=addHost&response=json

cc @sureshanaparti @harikrishna-patnala @nvazquez can you triage?

@cafecat6503 based on the logs, it seems your vSphere DC has no hosts:
2021-05-06 00:43:51,409 ERROR [c.c.h.v.m.VmwareManagerImpl] (qtp1644231115-16:ctx-9d55a0d4 ctx-5805610d) (logid:bda73b7f) Unable to find host from inventory path: /home-dc1/cloud-cluster/<my-esxi-hostfqdn>
2021-05-06 00:43:51,409 INFO  [c.c.h.v.VmwareServerDiscoverer] (qtp1644231115-16:ctx-9d55a0d4 ctx-5805610d) (logid:bda73b7f) Found 0 hosts.
...
2021-05-06 00:43:51,415 WARN  [c.c.r.ResourceManagerImpl] (qtp1644231115-16:ctx-9d55a0d4 ctx-5805610d) (logid:bda73b7f) Unable to find the server resources at http://<my-vCenter-fqdn>/home-dc1/cloud-cluster/<my-esxi-hostfqdn>

Can you if your DC has any host? (url in logs pointing to /home-dc1/cloud-cluster/)
You need to add your hosts to the cluster under a DC in vSphere before adding them in cloudstack. Also check the cluster name and DC name. (Do they match what you configured while you deployed the zone, or in the cluster where you're adding the host?)

Hi @cafecat6503 let us know if you still can reproduce the issue after the steps mentioned above by @rhtyd

こんにちは。
はい、ホストはcloudstackに追加する前にDCに追加されています。
DCの名前もclusterの名前も正しいです。 @rhtyd

@cafecat6503 based on the logs, CloudStack failed to find any hosts in the DC/cluster. Please try again, check the full path. You can confirm the path and list DC/hosts by using govc - https://github.com/vmware/govmomi/releases
And then try again to add the hosts to your CloudStack cluster.
(PS. I had to use google translate to understand what you meant - hope I got that right)

Thanks @cafecat6503 closing on your remark. Please try to add hosts using the right path, if you've the same issue again even after passing the right parameter, pl re-open the ticket.

authors: cafecat6503 nvazquez rhtyd

repo: apache/cloudstack


text:
[UI] feature request: deploy vm with param from previous page

Examples:
Select a network -> "View Instances" -> "Add Instance' , the network is selected by default.
Select a Template -> "View Instances" -> "Add Instance' , the template is selected by default.
ISSUE TYPE

Improvement Request

COMPONENT NAME

UI

CLOUDSTACK VERSION

4.16.0.0

CONFIGURATION

N/A
OS / ENVIRONMENT

N/A

Fixed in #5653

authors: sureshanaparti weizhouapache


text:
CLOUDSTACK-9565: Fix intermittent failure in test_oobm_zchange_password

Fixes intermittent integration smoke test failures caused in
test_oobm_zchange_password test.
The scope is limited to the integration test only, and full integration test suite is not necessary. We can only consider code reviews and merge on basis of Travis results.

Jenkins failure was due to git pull issue, not the PR changes. Pinging for quick review/merge -- @abhinandanprateek @murali-reddy @karuturi @koushik-das

Test seems to be passing now:
=== TestName: test_oobm_zchange_password | Status : SUCCESS ===

@LGTM on code review @rhtyd

LGTM

On basis of Travis result, manual test run and code reviews, I'm going ahead and merging this to avoid intermittent failures in upcoming tests.

authors: abhinandanprateek murali-reddy rhtyd


text:
Tungsten: Support multiple physical networks

Description
This PR fixes #7207

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

backend changes are needed as well
will do it

@blueorangutan package

@weizhouapache a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: el9 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 5580

@blueorangutan package

@weizhouapache a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: el9 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 5586

@blueorangutan package

@weizhouapache a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: el9 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 5587

@blueorangutan package

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: el9 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 5588

@blueorangutan package

@weizhouapache a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: el9 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 5593

Trillian test result (tid-6200)
Environment: kvm-rocky8 (x2), Advanced Networking with Mgmt server r8
Total time taken: 59188 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr7220-t6200-kvm-rocky8.zip
Smoke tests completed. 107 look OK, 1 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

test_08_upgrade_kubernetes_ha_cluster
Failure
820.38
test_kubernetes_clusters.py

@weizhouapache , should any of the tungsten fixes go in 4.18?

@weizhouapache , should any of the tungsten fixes go in 4.18?

@DaanHoogland
no critical issues fixed by this PR.

given the EOL for the tungsten project, maybe close this (for now postpone)


text:
Remove sensitive params (VmPassword, etc) from VMWork log

Description
The VM's password & other details sent via VM Details Map during VmWorkStart are logged as base64 encoded strings.
2024-01-22 11:22:53,879 DEBUG [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-4:ctx-8c25a1bb job-4690/job-4691 ctx-18a45cc5) (logid:76180ad6) Execute VM work job: com.cloud.vm.VmWorkStart{"dcId":1,"podId":1,"clusterId":1,"hostId":2,"rawParams":{"ConsiderLastHost":"rO0ABXQABHRydWU","VmPassword":"rO0ABXQADnNhdmVkX3Bhc3N3b3Jk"},"userId":2,"accountId":2,"vmId":415,"handlerName":"VirtualMachineManagerImpl"}
...
2024-01-22 11:22:59,456 DEBUG [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-4:ctx-8c25a1bb job-4690/job-4691 ctx-18a45cc5) (logid:76180ad6) Done executing VM work job: com.cloud.vm.VmWorkStart{"dcId":1,"podId":1,"clusterId":1,"hostId":2,"rawParams":{"ConsiderLastHost":"rO0ABXQABHRydWU","VmPassword":"rO0ABXQADnNhdmVkX3Bhc3N3b3Jk"},"userId":2,"accountId":2,"vmId":415,"handlerName":"VirtualMachineManagerImpl"}

This PR improves VMWork log to not include any sensitive params (VmPassword, etc).

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[x] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

Tested VM start and reboot operations, confirmed 'VmPassword' not shown in the log.
Log before changes =>
2024-01-22 11:22:53,879 DEBUG [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-4:ctx-8c25a1bb job-4690/job-4691 ctx-18a45cc5) (logid:76180ad6) Execute VM work job: com.cloud.vm.VmWorkStart{"dcId":1,"podId":1,"clusterId":1,"hostId":2,"rawParams":{"ConsiderLastHost":"rO0ABXQABHRydWU","VmPassword":"rO0ABXQADnNhdmVkX3Bhc3N3b3Jk"},"userId":2,"accountId":2,"vmId":415,"handlerName":"VirtualMachineManagerImpl"}

2024-01-22 11:22:59,456 DEBUG [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-4:ctx-8c25a1bb job-4690/job-4691 ctx-18a45cc5) (logid:76180ad6) Done executing VM work job: com.cloud.vm.VmWorkStart{"dcId":1,"podId":1,"clusterId":1,"hostId":2,"rawParams":{"ConsiderLastHost":"rO0ABXQABHRydWU","VmPassword":"rO0ABXQADnNhdmVkX3Bhc3N3b3Jk"},"userId":2,"accountId":2,"vmId":415,"handlerName":"VirtualMachineManagerImpl"}

Log after changes =>
2024-01-22 17:59:32,005 DEBUG [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-1:ctx-e027727c job-4730/job-4731 ctx-6c00584c) (logid:24c6cb7e) Execute VM work job: com.cloud.vm.VmWorkStart{"accountId":2,"dcId":1,"vmId":415,"hostId":2,"handlerName":"VirtualMachineManagerImpl","clusterId":1,"userId":2,"podId":1,"rawParams":{"ConsiderLastHost":"rO0ABXQABHRydWU"}}

2024-01-22 17:59:36,550 DEBUG [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-1:ctx-e027727c job-4730/job-4731 ctx-6c00584c) (logid:24c6cb7e) Done executing VM work job: com.cloud.vm.VmWorkStart{"accountId":2,"dcId":1,"vmId":415,"hostId":2,"handlerName":"VirtualMachineManagerImpl","clusterId":1,"userId":2,"podId":1,"rawParams":{"ConsiderLastHost":"rO0ABXQABHRydWU"}}

How did you try to break this feature and the system with this change?

@blueorangutan package

@sureshanaparti a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 8418

@blueorangutan test

@sureshanaparti a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

[SF] Trillian test result (tid-8922)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 49893 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr8553-t8922-kvm-centos7.zip
Smoke tests completed. 121 look OK, 0 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

LGTM - let's merge for 4.19.1.0, after the freeze/4.19.0.0 GA.


text:
no match of right hand value

Description
In the CouchDB logs I can see messages

[error] 2023-12-06T17:36:36 couchdb@db1a.example.com <> -------- CRASH REPORT Process  (<0.26820.435>) with 2 neighbors crashed with reason: no match of right hand value {'EXIT',noproc} at couch_file:pread_binary/2(line:166) <= couch_file:pread_term/2(line:155) <= couch_btree:get_node/2(line:474) <= couch_btree:lookup/3(line:314) <= couch_btree:lookup/2(line:304) <= couch_bt_engine:open_local_docs/2(line:388) <= couch_db:open_doc_int/3(line:1875) <= couch_db:open_doc/3(line:301); initial_call: {couch_index,init,['Argument__1']}, ancestors: [<0.20772.431>], message_queue_len: 0, links: [<0.20772.431>,<0.24852.435>], dictionary: [{io_priority,{view_update,<<"shards/80000000-9fffffff/xxxxxxxxxxxx...">>}}], trap_exit: false, status: running, heap_size: 2586, stack_size: 28, reductions: 6532

Looks like here no match of right hand value  need to be hanled.
Steps to Reproduce
Do not know
Expected Behaviour
Expected to print human readable error message.
Your Environment

CouchDB version used: apache/couchdb:3.3.2 docker image
Browser name and version: do not used
Operating system and version: CentOS 8 stream

Additional Context
N/A

Thanks @sergey-safarov. That looks like couch_file closed while a view_update write was pending.

noting that we would not 'handle' that unexpected value in the way you might imagine. it is the erlang way to assert the positive case, safe in the knowledge that anything unexpected will cause the erlang process to crash. so, while quite noisy as a long line, that looks like the right error handling.
the real question is why that erlang process crashed while it was in use. there might be other lines in the log file that tell us more.

Here installed 3 node cluster.
For two nodes log for this time range is clean.
Full error log for one node with issue follow.

[error] 2023-12-06T17:36:36.080062Z couchdb@db1a.example.com <0.26820.435> -------- CRASH REPORT Process  (<0.26820.435>) with 2 neighbors crashed with reason: no match of right hand value {'EXIT',noproc} at couch_file:pread_binary/2(line:166) <= couch_file:pread_term/2(line:155) <= couch_btree:get_node/2(line:474) <= couch_btree:lookup/3(line:314) <= couch_btree:lookup/2(line:304) <= couch_bt_engine:open_local_docs/2(line:388) <= couch_db:open_doc_int/3(line:1875) <= couch_db:open_doc/3(line:301); initial_call: {couch_index,init,['Argument__1']}, ancestors: [<0.20772.431>], message_queue_len: 0, links: [<0.20772.431>,<0.24852.435>], dictionary: [{io_priority,{view_update,<<"shards/80000000-9fffffff/account/8d/b1/c4...">>}}], trap_exit: false, status: running, heap_size: 2586, stack_size: 28, reductions: 6532
[error] 2023-12-06T17:36:36.079813Z couchdb@db1a.example.com <0.26820.435> -------- CRASH REPORT Process  (<0.26820.435>) with 2 neighbors crashed with reason: no match of right hand value {'EXIT',noproc} at couch_file:pread_binary/2(line:166) <= couch_file:pread_term/2(line:155) <= couch_btree:get_node/2(line:474) <= couch_btree:lookup/3(line:314) <= couch_btree:lookup/2(line:304) <= couch_bt_engine:open_local_docs/2(line:388) <= couch_db:open_doc_int/3(line:1875) <= couch_db:open_doc/3(line:301); initial_call: {couch_index,init,['Argument__1']}, ancestors: [<0.20772.431>], message_queue_len: 0, links: [<0.20772.431>,<0.24852.435>], dictionary: [{io_priority,{view_update,<<"shards/80000000-9fffffff/account/8d/b1/c4...">>}}], trap_exit: false, status: running, heap_size: 2586, stack_size: 28, reductions: 6532
extra: []
state: {st,"./data",index_server_2,couchdb_indexes_by_sig_2,couchdb_indexes_by_pid_2,couchdb_indexes_by_db_2}
last msg: redacted
[error] 2023-12-06T17:36:36.082938Z couchdb@db1a.example.com <0.283.0> -------- gen_server index_server_2 terminated with reason: no match of right hand value {'EXIT',noproc} at couch_file:pread_binary/2(line:166) <= couch_file:pread_term/2(line:155) <= couch_btree:get_node/2(line:474) <= couch_btree:lookup/3(line:314) <= couch_btree:lookup/2(line:304) <= couch_bt_engine:open_local_docs/2(line:388) <= couch_db:open_doc_int/3(line:1875) <= couch_db:open_doc/3(line:301) at couch_index_server:handle_info/2(line:207) <= gen_server:try_dispatch/4(line:695) <= gen_server:handle_msg/6(line:771) <= proc_lib:init_p_do_apply/3(line:226)
extra: []
state: {st,"./data",index_server_2,couchdb_indexes_by_sig_2,couchdb_indexes_by_pid_2,couchdb_indexes_by_db_2}
last msg: redacted
[error] 2023-12-06T17:36:36.083228Z couchdb@db1a.example.com <0.283.0> -------- gen_server index_server_2 terminated with reason: no match of right hand value {'EXIT',noproc} at couch_file:pread_binary/2(line:166) <= couch_file:pread_term/2(line:155) <= couch_btree:get_node/2(line:474) <= couch_btree:lookup/3(line:314) <= couch_btree:lookup/2(line:304) <= couch_bt_engine:open_local_docs/2(line:388) <= couch_db:open_doc_int/3(line:1875) <= couch_db:open_doc/3(line:301) at couch_index_server:handle_info/2(line:207) <= gen_server:try_dispatch/4(line:695) <= gen_server:handle_msg/6(line:771) <= proc_lib:init_p_do_apply/3(line:226)
[error] 2023-12-06T17:36:36.083514Z couchdb@db1a.example.com <0.283.0> -------- CRASH REPORT Process index_server_2 (<0.283.0>) with 1 neighbors exited with reason: no match of right hand value {'EXIT',noproc} at couch_file:pread_binary/2(line:166) <= couch_file:pread_term/2(line:155) <= couch_btree:get_node/2(line:474) <= couch_btree:lookup/3(line:314) <= couch_btree:lookup/2(line:304) <= couch_bt_engine:open_local_docs/2(line:388) <= couch_db:open_doc_int/3(line:1875) <= couch_db:open_doc/3(line:301) at couch_index_server:handle_info/2(line:207) <= gen_server:try_dispatch/4(line:695) <= gen_server:handle_msg/6(line:771) <= proc_lib:init_p_do_apply/3(line:226); initial_call: {couch_index_server,init,['Argument__1']}, ancestors: [couch_secondary_services,couch_sup,<0.253.0>], message_queue_len: 0, links: [<0.285.0>,<0.271.0>], dictionary: [], trap_exit: true, status: running, heap_size: 1598, stack_size: 28, reductions: 3560362
[error] 2023-12-06T17:36:36.083784Z couchdb@db1a.example.com <0.283.0> -------- CRASH REPORT Process index_server_2 (<0.283.0>) with 1 neighbors exited with reason: no match of right hand value {'EXIT',noproc} at couch_file:pread_binary/2(line:166) <= couch_file:pread_term/2(line:155) <= couch_btree:get_node/2(line:474) <= couch_btree:lookup/3(line:314) <= couch_btree:lookup/2(line:304) <= couch_bt_engine:open_local_docs/2(line:388) <= couch_db:open_doc_int/3(line:1875) <= couch_db:open_doc/3(line:301) at couch_index_server:handle_info/2(line:207) <= gen_server:try_dispatch/4(line:695) <= gen_server:handle_msg/6(line:771) <= proc_lib:init_p_do_apply/3(line:226); initial_call: {couch_index_server,init,['Argument__1']}, ancestors: [couch_secondary_services,couch_sup,<0.253.0>], message_queue_len: 0, links: [<0.285.0>,<0.271.0>], dictionary: [], trap_exit: true, status: running, heap_size: 1598, stack_size: 28, reductions: 3560362
[error] 2023-12-06T17:36:36.084049Z couchdb@db1a.example.com <0.271.0> -------- Supervisor couch_secondary_services had child index_server_2 started with couch_index_server:start_link(2) at <0.283.0> exit with reason no match of right hand value {'EXIT',noproc} at couch_file:pread_binary/2(line:166) <= couch_file:pread_term/2(line:155) <= couch_btree:get_node/2(line:474) <= couch_btree:lookup/3(line:314) <= couch_btree:lookup/2(line:304) <= couch_bt_engine:open_local_docs/2(line:388) <= couch_db:open_doc_int/3(line:1875) <= couch_db:open_doc/3(line:301) in context child_terminated
[error] 2023-12-06T17:36:36.084248Z couchdb@db1a.example.com <0.271.0> -------- Supervisor couch_secondary_services had child index_server_2 started with couch_index_server:start_link(2) at <0.283.0> exit with reason no match of right hand value {'EXIT',noproc} at couch_file:pread_binary/2(line:166) <= couch_file:pread_term/2(line:155) <= couch_btree:get_node/2(line:474) <= couch_btree:lookup/3(line:314) <= couch_btree:lookup/2(line:304) <= couch_bt_engine:open_local_docs/2(line:388) <= couch_db:open_doc_int/3(line:1875) <= couch_db:open_doc/3(line:301) in context child_terminated

After this timestamp and before CouchDB log is clean.
I also check CouchDB process uptime and found no CouchDB process restart at this time range.

Hello @nickva
Dev started database refactoring. Now we shrinking CouchDB size and I think now we cannot reproduce this error.
I will close ticket now. If some time we can stable reproduce issue, then will reopen.

authors: nickva rnewson sergey-safarov

repo: apache/couchdb


text:
Fix fn:exists when unparsing non-blocking expressions

Unparsing non-blocking expressions represent expression that are only
backwards referencing and will not require a suspension. This means that
the associated node must be final, and so we can immediately respond
that the element exists or not. Rethrowing the associated exception not
correct in this case. That is only correct when suspensions will be
involve, in which case that exception triggers the suspension logic.
DAFFODIL-2648

Could fn:count() have the same issue? Requires the array is finished.

fn:count() uses this same ExistsKind trait, so I think this fix for fn:exists() should also fix fn:count(). I'll add a test to make sure.

@olabusayoT This fix also addresses fn:count() which the big schema you are working on is using.
Can you review this PR so we can merge it?

+1 This fixed the isFinished error that was occurring in my large schema during unparsing.

I actually misread my run. I'm still getting the error, but the PR looks good so I'm keeping the approval

authors: mbeckerle olabusayoT stevedlawrence

repo: apache/daffodil


text:
chore: Simplify maven version extraction

Which issue does this PR close?

Closes #.
Rationale for this change

What changes are included in this PR?

How are these changes tested?

@edmondop Could you review?

repo: apache/datafusion-comet


text:
Add the possibility to work with plan clones directly in inline_table_scan

Is your feature request related to a problem or challenge?
I use the implementation of several TableProviders that allow for concurrent modification of the logical plan they store. A bit of context: this is necessary for implementing mutable views. Several views depend on view A and have TableProvider(A) in their logical plan. Then, when view A is modified, the logical plan for it is updated via some synchronization primitive, so all dependent views see the updated plan.
I would like the plans for the views to be inlined during the optimization phase in my implementation. However, the current TableProvider API forces me to return a shared reference to the internal logical plan for inlining, even though a copy would suffice.
I propose adding a get_logical_plan_cloned(...) method to the TableProvider trait, which would be used by passes that don't require a shared reference to the internal logical plan.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

There is the possible implementation
https://github.com/apache/datafusion/pull/12113

Couldn't you get the cloned by get_logical_plan with cloned() afterward? I don't get it why we need another API for cloned().

I have approximately the following struct:
struct MyProvider {
     plan: std::sync::Mutex<LogicalPlan>
}

impl TableProvider for MyProvider {
   ...
   fn get_logical_plan(&self) -> Option<&LogicalPlan> {
       //// ???
   }
}

(I use it to implement CREATE OR REPLACE VIEW).
But I can't implement get_logical_plan because MyProvider can't give the shared reference to the inner plan.

repo: apache/datafusion


text:
[Bug] [Module Name] Bug title

Search before asking

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

What happened

任务执行出现错误，这个错误原因不清楚，操作中发现任务一直在运行中，结束任务，再次运行还是这个情况；通过把任务导出，修改文件中任务的id，再导入进来，生成另一个任务，可以正常运行，但是后台日志一直不断输出错误日志
What you expected to happen
1、任务几分钟一直在执行中，实际几秒钟执行完毕，于是结束了任务，但是再次执行还是无法运行；
2、后台master日志一直打印，expected one but found 2，这个错误无法理解，希望能对这个问题做修复处理，感谢！！
How to reproduce
部署的为单节点，单台数据库，使用的为pgsql数据库作为元数据
Anything else
刚开始部署使用，目前部署5个任务，发现2次同类问题
Version
2.0.5
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

You should modify the title.

Please use the right title and describe in English, which can make more developers understand.
BTW, you should use screenshot or paste the error log stack, which can show your issue more clearly. Thanks.

authors: caishunfeng devosend hwfbest

repo: apache/dolphinscheduler


text:
调度flinksql 出现缺少jar包错误

Search before asking

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

What happened
利用dolphinscheduler调度flinksql，flink环境已经配置完全，运行查看报错The jar for the task is required.不去清楚少了什么jar包。

What you expected to happen
任务执行报错缺少jar包，不清楚缺少什么jar包
How to reproduce
无
Anything else
No response
Version
3.1.x
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Please describe in english.

authors: JanuaryFM SbloodyS


text:
[Feature][K8S Task] support node selector

Purpose of the pull request

This PR is a partial job of https://github.com/apache/dolphinscheduler/issues/13868.

Brief change log

Support same definition of NodeSelectorRequirement with https://kubernetes.io/docs/reference/kubernetes-api/common-definitions/node-selector-requirement/

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

It's a good feature for k8s task.
BTW, if ds deploy in k8s, node selector  is the same with  worker group. Maybe we can replace worker group with node selector in k8s.

It's a good feature for k8s task. BTW, if ds deploy in k8s, node selector is the same with worker group. Maybe we can replace worker group with node selector in k8s.

Agree with you, i can help with that.

Hi, @caishunfeng, @SbloodyS, can you help re-run CI?

Hi, @caishunfeng, @SbloodyS, can you help re-run CI?

Done.

authors: Radeity SbloodyS caishunfeng


text:
[Fix-9174] [Alert] Fix deduplication of alarm information

Purpose of the pull request
This pr will close https://github.com/apache/dolphinscheduler/issues/9174.

Add range for alarm suppression.
Optimize query logic.

see https://github.com/apache/dolphinscheduler/commit/f8ecb536b71d6f33b71c73930832b62890b84ea1
Supplement
I read commit https://github.com/apache/dolphinscheduler/commit/f8ecb536b71d6f33b71c73930832b62890b84ea1 and class org.apache.dolphinscheduler.dao.AlertDao.
It modified method org.apache.dolphinscheduler.dao.AlertDao#sendServerStopedAlert, but other logics have not changed. I speculate that the scene this friend is facing is just to reduce the frequency of redundant machine alarms in a time period. Judging by whether the content is equal is the actual demand. I think adding message ID to judge by message ID will lead to the invalidation of the logic he added and make this judgment meaningless, because it is difficult for multiple redundant machine actions of the same host to occur at the same time point (the ID will obviously be different).
In addition, if my understanding is correct, there is a hidden danger in the submission itself. The following logic will cause the same host crash not to be notified in the future.
where content = #{alert.content} and alert_status = #{alert.alertStatus.code}

and
ServerAlertContent serverStopAlertContent = ServerAlertContent.newBuilder()
        .type(serverType)
        .host(host)
        .event(AlertEvent.SERVER_DOWN)
        .warningLevel(AlertWarnLevel.SERIOUS).
        build();
String content = JSONUtils.toJsonString(Lists.newArrayList(serverStopAlertContent));

To sum up, the needs of both parties are:

The redundant machine will not be notified repeatedly for a period of time
Improve processing efficiency

A low-cost change can be to change the judgment condition of SQL to
where content = #{alert.content} and alert_status = #{alert.alertStatus.code} and create_time >= ${No alarm start time}

However, if table t_ds_alert is used for more alarms in the future, its data volume may be more than now. Even if field create_time is used as a condition, there is still room for optimization when using field content to make an equal judgment.
We can consider adding a field to calculate the content and other information combinations representing the message content to calculate the signature information, and use this field as the judgment basis.

Codecov Report

Merging #9371 (fcc6290) into dev (4a29c6a) will increase coverage by 0.02%.
The diff coverage is 47.20%.

:exclamation: Current head fcc6290 differs from pull request most recent head b861425. Consider uploading reports for the commit b861425 to get more accurate results

@@             Coverage Diff              @@
##                dev    #9371      +/-   ##
============================================
+ Coverage     39.98%   40.01%   +0.02%
- Complexity     4375     4387      +12
============================================
  Files           822      823       +1
  Lines         32924    32962      +38
  Branches       3656     3658       +2
============================================
+ Hits          13165    13189      +24
- Misses        18532    18542      +10
- Partials       1227     1231       +4

Impacted Files
Coverage Δ

...lugin/alert/wechat/WeChatAlertParamsConstants.java
0.00% <ø> (ø)

...uler/plugin/alert/wechat/WechatAppChatMessage.java
0.00% <0.00%> (ø)

...cheduler/plugin/alert/wechat/WechatAppMessage.java
0.00% <0.00%> (ø)

...inscheduler/api/controller/ExecutorController.java
40.00% <ø> (ø)

...er/api/service/impl/TaskDefinitionServiceImpl.java
24.01% <ø> (+0.05%)
:arrow_up:

...che/dolphinscheduler/common/enums/AlertStatus.java
0.00% <0.00%> (ø)

...uler/server/master/registry/ServerNodeManager.java
1.28% <0.00%> (ø)

.../org/apache/dolphinscheduler/dao/entity/Alert.java
65.38% <21.42%> (+19.11%)
:arrow_up:

...hinscheduler/plugin/alert/wechat/WeChatSender.java
29.78% <36.36%> (-7.79%)
:arrow_down:

...org/apache/dolphinscheduler/alert/AlertSender.java
71.92% <53.33%> (-2.11%)
: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 c294979...b861425. Read the comment docs.

@lenboo please review again, thanks.

@zhuangchong please help me with this review? Thx!

@zhuangchong  please review again, thx!

@zhuangchong  I resolve the code conflicts. please review again, thx!

@czeming Thanks for your contribution. This is a good beginning. Considering that it's your first contribution, I think we can get deep communication, you can contact me through mail or add WeChat(SbloodyS), when mail or added, please tell me who you are. I think I can help to familiar with the Dolphinscheduler if you meet with problems.

authors: SbloodyS codecov-commenter czeming


text:
feature fold weeks_sub/add on fe

Proposed changes
support folding weeks_sub/add on fe

Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

repo: apache/doris


text:
fixfix like predict

Proposed changes
fix like predict

Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


text:
fix cloud_p0 should not enable group_commit

Proposed changes
The cloud_p0 pipeline failed because run in group commit:
http://43.132.222.7:8111/buildConfiguration/Doris_DorisRegression_CloudP0/353352?buildTab=tests&name=load&status=failed&expandedTest=build%3A(id%3A353352)%2Cid%3A2000000951
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


text:
fix remove input slot for aggregate slot which is not materialized

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


text:
fix asan core should deconstruct filter entity in scope of query context

Proposed changes
Merge controller operation may create new memory and save in controller's object pool. So that should deconstruct the shared ptr in scope of query context to avoid asan check core.

run buildall


text:
fix ordinary users can see the processes of other users (#39747)

pick: https://github.com/apache/doris/pull/39747

run buildall


text:
featuresupport url domain functions

Proposed changes
support top_level_domain/first_significant_subdomain/cut_to_first_significant_subdomain functions
doc: https://github.com/apache/doris-website/pull/1230

need to add fe fold const when adding new scalar function to fe, which can refer to: https://selectdb.feishu.cn/wiki/BGfGwgY2uiQrK7krGUVcYJFknVg?from=from_copylink

run buildall

run buildall

run buildall


text:
Docker image doesn't work

Even though I docker pull apache/druid:0.19.0 and docker run apache/druid:0.19.0 following DockerHub, it does not work. I did it at my test directory, /Users/<user_name>/testenv.
My development environment is below.

MacBook Pro (13-inch, 2019, Four Thunderbolt 3 ports)
2.8 GHz Quad CoreIntel Core i7
16 GB 2133 MHz LPDDR3
Intel Iris Plus Graphics 655 1536 MB

Affected Version
0.19.0
Description
I have done a command docker system prune -a but neither did this work.

The error message is below.
❯ docker run apache/druid:0.19.0

2020-08-06T05:23:04+0000 startup service
Setting 172.17.0.2= in /runtime.properties
cat: can't open '/jvm.config': No such file or directory
2020-08-06T05:23:05,604 INFO [main] org.hibernate.validator.internal.util.Version - HV000001: Hibernate Validator 5.2.5.Final
2020-08-06T05:23:06,550 INFO [main] org.apache.druid.initialization.Initialization - Loading extension [druid-hdfs-storage], jars: jackson-annotations-2.10.2.jar, hadoop-mapreduce-client-common-2.8.5.jar, httpclient-4.5.10.jar, htrace-core4-4.0.1-incubating.jar, apacheds-kerberos-codec-2.0.0-M15.jar, jackson-mapper-asl-1.9.13.jar, commons-digester-1.8.jar, jetty-sslengine-6.1.26.jar, jackson-databind-2.10.2.jar, api-asn1-api-1.0.0-M20.jar, ion-java-1.0.2.jar, hadoop-mapreduce-client-shuffle-2.8.5.jar, asm-7.1.jar, jsp-api-2.1.jar, druid-hdfs-storage-0.19.0.jar, api-util-1.0.3.jar, json-smart-2.3.jar, jackson-core-2.10.2.jar, hadoop-client-2.8.5.jar, httpcore-4.4.11.jar, commons-collections-3.2.2.jar, hadoop-hdfs-client-2.8.5.jar, hadoop-annotations-2.8.5.jar, hadoop-auth-2.8.5.jar, xmlenc-0.52.jar, aws-java-sdk-s3-1.11.199.jar, commons-net-3.6.jar, nimbus-jose-jwt-4.41.1.jar, hadoop-common-2.8.5.jar, jackson-dataformat-cbor-2.10.2.jar, hadoop-yarn-server-common-2.8.5.jar, accessors-smart-1.2.jar, gson-2.2.4.jar, commons-configuration-1.6.jar, joda-time-2.10.5.jar, hadoop-aws-2.8.5.jar, aws-java-sdk-core-1.11.199.jar, commons-codec-1.13.jar, hadoop-mapreduce-client-app-2.8.5.jar, hadoop-yarn-api-2.8.5.jar, aws-java-sdk-kms-1.11.199.jar, jackson-core-asl-1.9.13.jar, curator-recipes-4.3.0.jar, hadoop-mapreduce-client-jobclient-2.8.5.jar, jcip-annotations-1.0-1.jar, jmespath-java-1.11.199.jar, hadoop-mapreduce-client-core-2.8.5.jar, commons-logging-1.1.1.jar, leveldbjni-all-1.8.jar, curator-framework-4.3.0.jar, hadoop-yarn-client-2.8.5.jar, apacheds-i18n-2.0.0-M15.jar
2020-08-06T05:23:06,574 INFO [main] org.apache.druid.initialization.Initialization - Loading extension [druid-kafka-indexing-service], jars: lz4-java-1.7.1.jar, kafka-clients-2.5.0.jar, druid-kafka-indexing-service-0.19.0.jar, zstd-jni-1.3.3-1.jar, snappy-java-1.1.7.3.jar
2020-08-06T05:23:06,576 INFO [main] org.apache.druid.initialization.Initialization - Loading extension [druid-datasketches], jars: druid-datasketches-0.19.0.jar, commons-math3-3.6.1.jar
usage: druid <command> [<args>]

The most commonly used druid commands are:
    help       Display help information
    index      Run indexing for druid
    internal   Processes that Druid runs "internally", you should rarely use these directly
    server     Run one of the Druid server types.
    tools      Various tools for working with Druid
    version    Returns Druid version information

See 'druid help <command>' for more information on a specific command.

❯ docker run apache/druid:0.19.0 version
2020-08-06T05:23:59+0000 startup service version
Setting druid.host=172.17.0.2 in /runtime.properties
cat: can't open '/jvm.config': No such file or directory
2020-08-06T05:24:00,780 INFO [main] org.hibernate.validator.internal.util.Version - HV000001: Hibernate Validator 5.2.5.Final
2020-08-06T05:24:01,763 INFO [main] org.apache.druid.initialization.Initialization - Loading extension [druid-hdfs-storage], jars: jackson-annotations-2.10.2.jar, hadoop-mapreduce-client-common-2.8.5.jar, httpclient-4.5.10.jar, htrace-core4-4.0.1-incubating.jar, apacheds-kerberos-codec-2.0.0-M15.jar, jackson-mapper-asl-1.9.13.jar, commons-digester-1.8.jar, jetty-sslengine-6.1.26.jar, jackson-databind-2.10.2.jar, api-asn1-api-1.0.0-M20.jar, ion-java-1.0.2.jar, hadoop-mapreduce-client-shuffle-2.8.5.jar, asm-7.1.jar, jsp-api-2.1.jar, druid-hdfs-storage-0.19.0.jar, api-util-1.0.3.jar, json-smart-2.3.jar, jackson-core-2.10.2.jar, hadoop-client-2.8.5.jar, httpcore-4.4.11.jar, commons-collections-3.2.2.jar, hadoop-hdfs-client-2.8.5.jar, hadoop-annotations-2.8.5.jar, hadoop-auth-2.8.5.jar, xmlenc-0.52.jar, aws-java-sdk-s3-1.11.199.jar, commons-net-3.6.jar, nimbus-jose-jwt-4.41.1.jar, hadoop-common-2.8.5.jar, jackson-dataformat-cbor-2.10.2.jar, hadoop-yarn-server-common-2.8.5.jar, accessors-smart-1.2.jar, gson-2.2.4.jar, commons-configuration-1.6.jar, joda-time-2.10.5.jar, hadoop-aws-2.8.5.jar, aws-java-sdk-core-1.11.199.jar, commons-codec-1.13.jar, hadoop-mapreduce-client-app-2.8.5.jar, hadoop-yarn-api-2.8.5.jar, aws-java-sdk-kms-1.11.199.jar, jackson-core-asl-1.9.13.jar, curator-recipes-4.3.0.jar, hadoop-mapreduce-client-jobclient-2.8.5.jar, jcip-annotations-1.0-1.jar, jmespath-java-1.11.199.jar, hadoop-mapreduce-client-core-2.8.5.jar, commons-logging-1.1.1.jar, leveldbjni-all-1.8.jar, curator-framework-4.3.0.jar, hadoop-yarn-client-2.8.5.jar, apacheds-i18n-2.0.0-M15.jar
2020-08-06T05:24:01,787 INFO [main] org.apache.druid.initialization.Initialization - Loading extension [druid-kafka-indexing-service], jars: lz4-java-1.7.1.jar, kafka-clients-2.5.0.jar, druid-kafka-indexing-service-0.19.0.jar, zstd-jni-1.3.3-1.jar, snappy-java-1.1.7.3.jar
2020-08-06T05:24:01,789 INFO [main] org.apache.druid.initialization.Initialization - Loading extension [druid-datasketches], jars: druid-datasketches-0.19.0.jar, commons-math3-3.6.1.jar
ERROR!!!!
Found unexpected parameters: [version]
===
usage: druid <command> [<args>]

The most commonly used druid commands are:
    help       Display help information
    index      Run indexing for druid
    internal   Processes that Druid runs "internally", you should rarely use these directly
    server     Run one of the Druid server types.
    tools      Various tools for working with Druid
    version    Returns Druid version information

See 'druid help <command>' for more information on a specific command.

This was just because of my Docker preference:cry:
I changed my memory allocation from 2GB to 6GB, which resulted in success!

repo: apache/druid


text:
GoogleProtobuf 对象泛化调用

操作步骤
点击参考链接无效

期望
链接正常访问

I'll fix it

repo: apache/dubbo-website


text:
Dubbo 3.2.2 Triple协议并发场景下偶发数组越界异常

具体报错如下：
Caused by: java.util.concurrent.ExecutionException: java.lang.ArrayIndexOutOfBoundsException: arraycopy: last destination index 1086 out of bounds for double
atjava.base/java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:395)
at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2070)
at org.apache.dubbo.rpc.AsyncRpcResult.getAppResponse(AsyncRpcResult.java:161)
89 common frames omitted
Caused by: java.lang.ArrayIndex0utOfBoundsException: arraycopy: last destination index 1086 out of bounds for double[1050]
at java.base/java.lang.System.arraycopy(Native Method)
at com.tdunning.math.stats.MergingDigest.merge(MergingDigest.java:381)
at com.tdunning.math.stats.MergingDigest.mergeNewValues(MergingDigest.java:363)
at com.tdunning.math.stats.MergingDigest.mergeNewValues(MergingDigest.java:353)
at com.tdunning.math.stats.MergingDigest.add(MergingDigest.java:259)
at com.tdunning.math.stats.MergingDigest.add(MergingDigest.java:251)
at com.tdunning.math.stats.AbstractTDigest.add(AbstractTDigest.java:129)
at org.apache.dubbo.metrics.aggregate.TimeWindowQuantile.add(TimeWindowOuantile.iava:51)
at org.apache.dubbo.metrics.collector.AggregateMetricsCollector.onRTEvent(AggregateMetricsCollector.java:92)
atorg.apache.dubbo.metrics.collector.AggregateMetricsCollector.onEvent(AggregateMetricsCollector.java:82)
at org.apache.dubbo.metrics.event.SimpleMetricsEventMulticaster.publishEvent(SimpleMetricsEventMulticaster.iava:48)
atorg.apache.dubbo.metrics.collector.sample.MethodMetricsSampler.lambda$rtConfigure$3(MethodMetricsSampler.java:61)
at org.apache.dubbo.metrics.collector.sample.SimpleMetricsCountSampler.addRT(SimpleMetricsCountSampler.java:120)
at org.apache.dubbo.metrics.filter.MethodMetricsInterceptor.rtTime(MethodMetricsInterceptor.java:97)
at org. apache.dubbo.metrics.filter.MethodMetricsInterceptor.onCompleted(MethodMetricsInterceptor.java:101)
at org.apache.dubbo.metrics.filter.MethodMetricsInterceptor.afterMethod(MethodMetricsInterceptor.java:58)
at org.apache.dubbo.metrics.filter.MetricsFilter.onResponse(MetricsFilter.iava:64)
atorg.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CallbackRegistrationInvoker.lambda$invoke$1(FilterChainBuilder.java:218)
atorg.apache.dubbo.rpc.AsyncRpcResult.lambda$whenCompleteWithContext$0(AsyncRpcResult.java:228)
at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859)
at java.base/java.util.concurrent.CompletableFuture.uniWhenCompleteStage(CompletableFuture.java:883)
at java.base/java.util.concurrent.CompletableFuture.whenComplete(CompletableFuture.java:2322)
at org.apache.dubbo.rpc.AsyncRpcResult.whenCompleteWithContext(AsyncRpcResult.java:224)
atorg.apache.dubbo.rpc.cluster.filter.FilterChainBuilder$CallbackRegistrationInvoker.invoke(FilterChainBuilder.java:195)

@songxiaosheng PTAL

@DoctorFung 确认下你们dubbo-spring-boot-observability-starter版本号是什么呀

他用的3.2.0，升级3.2.1+即可

authors: DoctorFung EarthChen songxiaosheng wxbty

repo: apache/dubbo


text:
不使用dubbo的默认日志框架，启动时会报拒绝连接错误

[ ] I have searched the issues of this repository and believe that this is not a duplicate.
[ ] I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.8
Operating System version: deepin V20 社区版
Java version: 1.8

Steps to reproduce this issue

在springboot启动main方法里添加如下代码：

System.setProperty("dubbo.application.logger","slf4j");

Pls. provide [GitHub address] to reproduce this issue.
Expected Result
希望项目启动时不要报异常
Actual Result
如果使用dubbo的默认日志框架启动时不会报任何错误。
使用了指定的slf4j就会报如下异常，但并不影响使用。
为了不看见异常，我暂时使用默认的log4j
2020-12-26 19:01:40.203  INFO 10072 --- [           main] org.apache.dubbo.config.ServiceConfig    :  [DUBBO] Export dubbo service com.zbi.admin.service.PermissionService to local registry url : injvm://127.0.0.1/com.zbi.admin.service.PermissionService?anyhost=true&application=zbi-admin-server&bind.ip=192.168.31.90&bind.port=20880&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&group=permissionServiceImpl&interface=com.zbi.admin.service.PermissionService&logger=slf4j&methods=query,update,del,delete,queryList,queryColumns,findPermissionByIds,queryById&pid=10072&qos.enable=false&release=2.7.8&side=provider&timestamp=1608980500199, dubbo version: 2.7.8, current host: 192.168.31.90
2020-12-26 19:01:40.203  INFO 10072 --- [           main] org.apache.dubbo.config.ServiceConfig    :  [DUBBO] Register dubbo service com.zbi.admin.service.PermissionService url dubbo://192.168.31.90:20880/com.zbi.admin.service.PermissionService?anyhost=true&application=zbi-admin-server&bind.ip=192.168.31.90&bind.port=20880&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&group=permissionServiceImpl&interface=com.zbi.admin.service.PermissionService&logger=slf4j&methods=query,update,del,delete,queryList,queryColumns,findPermissionByIds,queryById&pid=10072&qos.enable=false&release=2.7.8&side=provider&timestamp=1608980500199 to registry registry://localhost:9090/org.apache.dubbo.registry.RegistryService?application=zbi-admin-server&dubbo=2.0.2&logger=slf4j&pid=10072&qos.enable=false&registry=spring-cloud&release=2.7.8&timestamp=1608980500199, dubbo version: 2.7.8, current host: 192.168.31.90
2020-12-26 19:01:40.204  INFO 10072 --- [           main] c.a.c.dubbo.registry.DubboCloudRegistry  :  [DUBBO] Register: dubbo://192.168.31.90:20880/com.zbi.admin.service.PermissionService?anyhost=true&application=zbi-admin-server&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&group=permissionServiceImpl&interface=com.zbi.admin.service.PermissionService&logger=slf4j&methods=query,update,del,delete,queryList,queryColumns,findPermissionByIds,queryById&pid=10072&release=2.7.8&side=provider&timestamp=1608980500199, dubbo version: 2.7.8, current host: 192.168.31.90
2020-12-26 19:01:40.205  INFO 10072 --- [           main] c.a.c.dubbo.registry.DubboCloudRegistry  :  [DUBBO] Subscribe: provider://192.168.31.90:20880/com.zbi.admin.service.PermissionService?anyhost=true&application=zbi-admin-server&bind.ip=192.168.31.90&bind.port=20880&category=configurators&check=false&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&group=permissionServiceImpl&interface=com.zbi.admin.service.PermissionService&logger=slf4j&methods=query,update,del,delete,queryList,queryColumns,findPermissionByIds,queryById&pid=10072&qos.enable=false&release=2.7.8&side=provider&timestamp=1608980500199, dubbo version: 2.7.8, current host: 192.168.31.90
2020-12-26 19:01:40.206  INFO 10072 --- [           main] m.DynamicConfigurationServiceNameMapping :  [DUBBO] Dubbo service[permissionServiceImpl] mapped to interface name[com.zbi.admin.service.PermissionService]., dubbo version: 2.7.8, current host: 192.168.31.90
2020-12-26 19:01:40.213  INFO 10072 --- [           main] org.apache.dubbo.config.ServiceConfig    :  [DUBBO] No valid ip found from environment, try to find valid host from DNS., dubbo version: 2.7.8, current host: 192.168.31.90
2020-12-26 19:01:40.213  WARN 10072 --- [           main] org.apache.dubbo.config.ServiceConfig    :  [DUBBO] 拒绝连接, dubbo version: 2.7.8, current host: 192.168.31.90

java.net.ConnectException: 拒绝连接
	at java.net.PlainSocketImpl.socketConnect(Native Method) ~[na:1.8.0_60]
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[na:1.8.0_60]
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[na:1.8.0_60]
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[na:1.8.0_60]
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[na:1.8.0_60]
	at java.net.Socket.connect(Socket.java:589) ~[na:1.8.0_60]
	at org.apache.dubbo.config.ServiceConfig.findConfigedHosts(ServiceConfig.java:588) [dubbo-2.7.8.jar:2.7.8]
	at org.apache.dubbo.config.ServiceConfig.doExportUrlsFor1Protocol(ServiceConfig.java:443) [dubbo-2.7.8.jar:2.7.8]
	at org.apache.dubbo.config.ServiceConfig.doExportUrls(ServiceConfig.java:325) [dubbo-2.7.8.jar:2.7.8]
	at org.apache.dubbo.config.ServiceConfig.doExport(ServiceConfig.java:300) [dubbo-2.7.8.jar:2.7.8]
	at org.apache.dubbo.config.ServiceConfig.export(ServiceConfig.java:206) [dubbo-2.7.8.jar:2.7.8]
	at org.apache.dubbo.config.bootstrap.DubboBootstrap.lambda$exportServices$15(DubboBootstrap.java:1103) [dubbo-2.7.8.jar:2.7.8]
	at java.util.HashMap$Values.forEach(HashMap.java:972) ~[na:1.8.0_60]
	at org.apache.dubbo.config.bootstrap.DubboBootstrap.exportServices(DubboBootstrap.java:1090) [dubbo-2.7.8.jar:2.7.8]
	at org.apache.dubbo.config.bootstrap.DubboBootstrap.start(DubboBootstrap.java:901) [dubbo-2.7.8.jar:2.7.8]
	at org.apache.dubbo.config.spring.context.DubboBootstrapApplicationListener.onContextRefreshedEvent(DubboBootstrapApplicationListener.java:59) ~[dubbo-2.7.8.jar:2.7.8]
	at org.apache.dubbo.config.spring.context.DubboBootstrapApplicationListener.onApplicationContextEvent(DubboBootstrapApplicationListener.java:52) ~[dubbo-2.7.8.jar:2.7.8]
	at org.apache.dubbo.config.spring.context.OneTimeExecutionApplicationContextEventListener.onApplicationEvent(OneTimeExecutionApplicationContextEventListener.java:40) ~[dubbo-2.7.8.jar:2.7.8]
	at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172) ~[spring-context-5.2.8.RELEASE.jar:5.2.8.RELEASE]
	at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165) ~[spring-context-5.2.8.RELEASE.jar:5.2.8.RELEASE]
	at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139) ~[spring-context-5.2.8.RELEASE.jar:5.2.8.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:404) ~[spring-context-5.2.8.RELEASE.jar:5.2.8.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:361) ~[spring-context-5.2.8.RELEASE.jar:5.2.8.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:898) ~[spring-context-5.2.8.RELEASE.jar:5.2.8.RELEASE]
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.finishRefresh(ServletWebServerApplicationContext.java:162) ~[spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:554) ~[spring-context-5.2.8.RELEASE.jar:5.2.8.RELEASE]
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:141) ~[spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:747) ~[spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397) ~[spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:315) ~[spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1226) ~[spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1215) ~[spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
	at com.zbi.admin.AdminServerApplication.main(AdminServerApplication.java:32) ~[classes/:na]

[ ]  I have searched the issues of this repository and believe that this is not a duplicate.
[ ]  I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.8
Operating System version: deepin V20 社区版
Java version: 1.8

Steps to reproduce this issue

在springboot启动main方法里添加如下代码：

System.setProperty("dubbo.application.logger","slf4j");

Pls. provide [GitHub address] to reproduce this issue.
Expected Result
希望项目启动时不要报异常
Actual Result
如果使用dubbo的默认日志框架启动时不会报任何错误。
使用了指定的slf4j就会报如下异常，但并不影响使用。
为了不看见异常，我暂时使用默认的log4j
2020-12-26 19:01:40.203  INFO 10072 --- [           main] org.apache.dubbo.config.ServiceConfig    :  [DUBBO] Export dubbo service com.zbi.admin.service.PermissionService to local registry url : injvm://127.0.0.1/com.zbi.admin.service.PermissionService?anyhost=true&application=zbi-admin-server&bind.ip=192.168.31.90&bind.port=20880&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&group=permissionServiceImpl&interface=com.zbi.admin.service.PermissionService&logger=slf4j&methods=query,update,del,delete,queryList,queryColumns,findPermissionByIds,queryById&pid=10072&qos.enable=false&release=2.7.8&side=provider&timestamp=1608980500199, dubbo version: 2.7.8, current host: 192.168.31.90
2020-12-26 19:01:40.203  INFO 10072 --- [           main] org.apache.dubbo.config.ServiceConfig    :  [DUBBO] Register dubbo service com.zbi.admin.service.PermissionService url dubbo://192.168.31.90:20880/com.zbi.admin.service.PermissionService?anyhost=true&application=zbi-admin-server&bind.ip=192.168.31.90&bind.port=20880&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&group=permissionServiceImpl&interface=com.zbi.admin.service.PermissionService&logger=slf4j&methods=query,update,del,delete,queryList,queryColumns,findPermissionByIds,queryById&pid=10072&qos.enable=false&release=2.7.8&side=provider&timestamp=1608980500199 to registry registry://localhost:9090/org.apache.dubbo.registry.RegistryService?application=zbi-admin-server&dubbo=2.0.2&logger=slf4j&pid=10072&qos.enable=false&registry=spring-cloud&release=2.7.8&timestamp=1608980500199, dubbo version: 2.7.8, current host: 192.168.31.90
2020-12-26 19:01:40.204  INFO 10072 --- [           main] c.a.c.dubbo.registry.DubboCloudRegistry  :  [DUBBO] Register: dubbo://192.168.31.90:20880/com.zbi.admin.service.PermissionService?anyhost=true&application=zbi-admin-server&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&group=permissionServiceImpl&interface=com.zbi.admin.service.PermissionService&logger=slf4j&methods=query,update,del,delete,queryList,queryColumns,findPermissionByIds,queryById&pid=10072&release=2.7.8&side=provider&timestamp=1608980500199, dubbo version: 2.7.8, current host: 192.168.31.90
2020-12-26 19:01:40.205  INFO 10072 --- [           main] c.a.c.dubbo.registry.DubboCloudRegistry  :  [DUBBO] Subscribe: provider://192.168.31.90:20880/com.zbi.admin.service.PermissionService?anyhost=true&application=zbi-admin-server&bind.ip=192.168.31.90&bind.port=20880&category=configurators&check=false&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&group=permissionServiceImpl&interface=com.zbi.admin.service.PermissionService&logger=slf4j&methods=query,update,del,delete,queryList,queryColumns,findPermissionByIds,queryById&pid=10072&qos.enable=false&release=2.7.8&side=provider&timestamp=1608980500199, dubbo version: 2.7.8, current host: 192.168.31.90
2020-12-26 19:01:40.206  INFO 10072 --- [           main] m.DynamicConfigurationServiceNameMapping :  [DUBBO] Dubbo service[permissionServiceImpl] mapped to interface name[com.zbi.admin.service.PermissionService]., dubbo version: 2.7.8, current host: 192.168.31.90
2020-12-26 19:01:40.213  INFO 10072 --- [           main] org.apache.dubbo.config.ServiceConfig    :  [DUBBO] No valid ip found from environment, try to find valid host from DNS., dubbo version: 2.7.8, current host: 192.168.31.90
2020-12-26 19:01:40.213  WARN 10072 --- [           main] org.apache.dubbo.config.ServiceConfig    :  [DUBBO] 拒绝连接, dubbo version: 2.7.8, current host: 192.168.31.90

java.net.ConnectException: 拒绝连接
	at java.net.PlainSocketImpl.socketConnect(Native Method) ~[na:1.8.0_60]
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ~[na:1.8.0_60]
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) ~[na:1.8.0_60]
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) ~[na:1.8.0_60]
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[na:1.8.0_60]
	at java.net.Socket.connect(Socket.java:589) ~[na:1.8.0_60]
	at org.apache.dubbo.config.ServiceConfig.findConfigedHosts(ServiceConfig.java:588) [dubbo-2.7.8.jar:2.7.8]
	at org.apache.dubbo.config.ServiceConfig.doExportUrlsFor1Protocol(ServiceConfig.java:443) [dubbo-2.7.8.jar:2.7.8]
	at org.apache.dubbo.config.ServiceConfig.doExportUrls(ServiceConfig.java:325) [dubbo-2.7.8.jar:2.7.8]
	at org.apache.dubbo.config.ServiceConfig.doExport(ServiceConfig.java:300) [dubbo-2.7.8.jar:2.7.8]
	at org.apache.dubbo.config.ServiceConfig.export(ServiceConfig.java:206) [dubbo-2.7.8.jar:2.7.8]
	at org.apache.dubbo.config.bootstrap.DubboBootstrap.lambda$exportServices$15(DubboBootstrap.java:1103) [dubbo-2.7.8.jar:2.7.8]
	at java.util.HashMap$Values.forEach(HashMap.java:972) ~[na:1.8.0_60]
	at org.apache.dubbo.config.bootstrap.DubboBootstrap.exportServices(DubboBootstrap.java:1090) [dubbo-2.7.8.jar:2.7.8]
	at org.apache.dubbo.config.bootstrap.DubboBootstrap.start(DubboBootstrap.java:901) [dubbo-2.7.8.jar:2.7.8]
	at org.apache.dubbo.config.spring.context.DubboBootstrapApplicationListener.onContextRefreshedEvent(DubboBootstrapApplicationListener.java:59) ~[dubbo-2.7.8.jar:2.7.8]
	at org.apache.dubbo.config.spring.context.DubboBootstrapApplicationListener.onApplicationContextEvent(DubboBootstrapApplicationListener.java:52) ~[dubbo-2.7.8.jar:2.7.8]
	at org.apache.dubbo.config.spring.context.OneTimeExecutionApplicationContextEventListener.onApplicationEvent(OneTimeExecutionApplicationContextEventListener.java:40) ~[dubbo-2.7.8.jar:2.7.8]
	at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:172) ~[spring-context-5.2.8.RELEASE.jar:5.2.8.RELEASE]
	at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:165) ~[spring-context-5.2.8.RELEASE.jar:5.2.8.RELEASE]
	at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139) ~[spring-context-5.2.8.RELEASE.jar:5.2.8.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:404) ~[spring-context-5.2.8.RELEASE.jar:5.2.8.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:361) ~[spring-context-5.2.8.RELEASE.jar:5.2.8.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:898) ~[spring-context-5.2.8.RELEASE.jar:5.2.8.RELEASE]
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.finishRefresh(ServletWebServerApplicationContext.java:162) ~[spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:554) ~[spring-context-5.2.8.RELEASE.jar:5.2.8.RELEASE]
	at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:141) ~[spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:747) ~[spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:397) ~[spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:315) ~[spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1226) ~[spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1215) ~[spring-boot-2.2.5.RELEASE.jar:2.2.5.RELEASE]
	at com.zbi.admin.AdminServerApplication.main(AdminServerApplication.java:32) ~[classes/:na]

有个办法解决，你可以参考一下
在dubbo的配置中，目前（2021年11月23日16:31:34）的版本，在使用springcloud的discovery的时候 是可以不用配置registry.address的，你可以配置上如下，配置成内网IP。看看能不能解决你的问题。
dubbo:
  cloud:
    subscribed-services: ${spring.application.name}
  scan:
    base-packages: com.example
  protocol:
    name: dubbo
    port: 20880
  registry:
    address: spring-cloud://_**这里写内网IP**_

authors: imyiren longzhaobi


text:
dubbo使用nacos做多注册中心，重启服务会导致provider被覆盖

Environment

Dubbo version: 2.7.12
Java version: 1.8

Steps to reproduce this issue

配置多个nacos注册中心
启动provider和consumer服务
重启某个注册中心的provider服务，会导致另一个注册中心的provider也变成这个重启的provider

源码解读发现逻辑问题

com.alibaba.nacos.client.naming.core.HostReactor#processServiceJson里会发布InstancesChangeEvent，这个事件会通知所有naocs注册中心的服务。
会触发这个方法org.apache.dubbo.registry.nacos.NacosRegistry#subscribeEventListener里定义的eventListener。
之后org.apache.dubbo.registry.integration.RegistryDirectory#refreshOverrideAndInvoker 会更新routerChain.setInvokers(newInvokers)。
这里的newInvokers代表重启后的服务provider
最后的结果就导致不同nacos注册中心的对应的RegistryDirectory对象，invokers都被更新成了一个

repeat：https://github.com/apache/dubbo/issues/8838

authors: CrazyHZM zjutbang


text:
JsonUtil jackson impl

commit to 3.2 https://github.com/apache/dubbo/pull/10960

Codecov Report

Merging #10970 (cd60ace) into 3.2 (9d4cb1a) will decrease coverage by 0.07%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##                3.2   #10970      +/-   ##
============================================
- Coverage     20.67%   20.60%   -0.08%
  Complexity       14       14
============================================
  Files          1440     1442       +2
  Lines         59659    59863     +204
  Branches       8751     8773      +22
============================================
- Hits          12337    12335       -2
- Misses        45245    45450     +205
- Partials       2077     2078       +1

Impacted Files
Coverage Δ

...org/apache/dubbo/common/json/impl/JacksonImpl.java
0.00% <0.00%> (ø)

.../java/org/apache/dubbo/common/utils/JsonUtils.java
25.71% <0.00%> (-1.56%)
:arrow_down:

...rg/apache/dubbo/common/url/component/URLParam.java
56.39% <0.00%> (-0.48%)
:arrow_down:

...dubbo/common/status/support/LoadStatusChecker.java
41.66% <0.00%> (ø)

...ubbo/registry/nacos/NacosNamingServiceWrapper.java
0.00% <0.00%> (ø)

...o/registry/nacos/util/NacosNamingServiceUtils.java
0.00% <0.00%> (ø)

...e/dubbo/registry/nacos/NacosConnectionManager.java
0.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

authors: JavaHello codecov-commenter