-
Notifications
You must be signed in to change notification settings - Fork 6.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix deadlock problem when using elasticsearch-client-7.0.0 #5775
Conversation
lang-mustache-client-7.5.0.jar | ||
mapper-extras-client-7.5.0.jar | ||
parent-join-client-7.5.0.jar | ||
rank-eval-client-7.5.0.jar |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You need to update LICENSE including
- Versions of
lang-mustache-client
andparent-join-client
- Add
mapper-extras-client
with license as we missed before - Add
rank-eval-client
with license as we missed before, both 6.3.2(es6 package) and 7.5.0(you updated)
@kezhenxu94 What ES version do we use to test? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And you missed the change log update.
Codecov Report
@@ Coverage Diff @@
## master #5775 +/- ##
============================================
- Coverage 51.51% 44.83% -6.69%
+ Complexity 3465 2205 -1260
============================================
Files 1642 1632 -10
Lines 35112 34820 -292
Branches 3833 3985 +152
============================================
- Hits 18089 15611 -2478
- Misses 16125 18338 +2213
+ Partials 898 871 -27 Continue to review full report at Codecov.
|
…t7_update # Conflicts: # CHANGES.md
done. |
6.3.2 and 7.4.2 |
@zifeihan CI logs show, the dependency changes are not accurate, please recheck. You could use the same scripts we used in the CI, https://github.com/apache/skywalking/tree/master/tools/dependencies. |
done. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@zifeihan I have asked @kezhenxu94 to adjust e2e to text 7.0.0 and higher version, like 7.9.3(latest) to verify the compatibility. Let's wait for that. |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are several other libs updated in this according to known-oap-backend-dependencies-es7.txt change log.
So, the LICENSE still needs some polish. In the current, we missed ES7 dependency version, such as hppc 0.7.1
, which is ES6 depending.
@zifeihan Could you help on adding the ES6 dependency versions to the LICENSE file like I commented for the ES client.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is much better now.
Notice this issue may cause the log "Grpc server thread pool is full, rejecting the task". |
Thanks submit this, why it cause this error log? our production environment processes tens of billions of data every day, and we have never found such logs. |
I found a lot of such logs in the oap log.
|
@zifeihan I don't mean our scene is the same. The bug of the es client also cause other thread-block problems which this merge will fix. |
Have you upgraded to version 8.3.0 or higher? If so, please dump thread to analyze the root cause of the problem. If not, I think this problem may be caused by the deadlock of es-client. |
I will upgrade to 8.3.0 soon. Yes, I am sure It's the problem of es-client. |
Fix deadlock problem when using es
Hello, a few days ago, there was a problem that es data could not be written in our production environment. We dump the thread stack of the production environment. After analysis, it is found that es client has a deadlock problem when writing data.thread dump thread dump. In order to solve the problem, I checked many related materials, and found that this problem has been fixed in elasticsearch-client version 7.5.0. Prevent deadlock by using separate schedulers
so i update the elasticsearch client 7.0.0 to elasticsearch client 7.5.0.
In order to avoid es compatibility issues, I use elasticsearch server 7.0.0 as data storage. Tested whether the ui function is normal, and checked whether the OAP is abnormal during operation. The test results show that everything is normal. and the current elasticsearch server in our production environment is 7.2.0, and we are also using elasticsearch client 7.5.0. It has been running stably for 3 days without any compatibility issues.