Skip to content
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

feat: local dynconfig notifies data in client #2264

Merged
merged 1 commit into from
Apr 12, 2023
Merged

Conversation

gaius-qi
Copy link
Member

Dfdaemon will fail the health check if there is no available scheduler address. So in the case of local dynconfig, the address of scheduler should be passed. For dfdaemon health check, please refer to #2130.

Description

Dfdaemon will fail the health check if there is no available scheduler address. So in the case of local dynconfig, the address of scheduler should be passed. For dfdaemon health check, please refer to #2130.

Related Issue

Motivation and Context

Screenshots (if appropriate)

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation Update (if none of the other choices apply)

Checklist

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.

@gaius-qi gaius-qi added enhancement New feature or request client labels Apr 12, 2023
@gaius-qi gaius-qi added this to the v2.1.0 milestone Apr 12, 2023
@gaius-qi gaius-qi self-assigned this Apr 12, 2023
@gaius-qi gaius-qi requested a review from a team as a code owner April 12, 2023 03:09
hyy0322
hyy0322 previously approved these changes Apr 12, 2023
@codecov
Copy link

codecov bot commented Apr 12, 2023

Codecov Report

Merging #2264 (4ca5f1f) into main (f6a3c7e) will decrease coverage by 0.02%.
The diff coverage is 0.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #2264      +/-   ##
==========================================
- Coverage   49.61%   49.60%   -0.02%     
==========================================
  Files         146      146              
  Lines       19513    19526      +13     
==========================================
+ Hits         9682     9685       +3     
- Misses       9233     9245      +12     
+ Partials      598      596       -2     
Flag Coverage Δ
Object-compatibility-e2etests ?
e2etests ?
unittests 49.60% <0.00%> (-0.02%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
client/config/dynconfig_local.go 38.63% <0.00%> (-6.70%) ⬇️

... and 1 file with indirect coverage changes

Dfdaemon will fail the health check if there is no available scheduler address.
So in the case of local dynconfig, the address of scheduler should be passed.
For dfdaemon health check, please refer to #2130.

Signed-off-by: Gaius <[email protected]>
Copy link
Member

@jim3ma jim3ma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@gaius-qi gaius-qi merged commit f2e42bc into main Apr 12, 2023
@gaius-qi gaius-qi deleted the feature/dynconfig branch April 12, 2023 03:41
lilongfeng0902 pushed a commit to lilongfeng0902/Dragonfly2 that referenced this pull request May 15, 2023
Dfdaemon will fail the health check if there is no available scheduler address.
So in the case of local dynconfig, the address of scheduler should be passed.
For dfdaemon health check, please refer to dragonflyoss#2130.

Signed-off-by: Gaius <[email protected]>
Signed-off-by: 李龙峰 <[email protected]>
gaius-qi added a commit that referenced this pull request Jun 28, 2023
Dfdaemon will fail the health check if there is no available scheduler address.
So in the case of local dynconfig, the address of scheduler should be passed.
For dfdaemon health check, please refer to #2130.

Signed-off-by: Gaius <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants