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

[PIP-82] [pulsar-broker] Resource group service, usage-data gathering… #10204

Merged
merged 1 commit into from
Apr 16, 2021

Conversation

kaushik-develop
Copy link
Contributor

@kaushik-develop kaushik-develop commented Apr 12, 2021

… and quota-calculation

(If this PR fixes a github issue, please add Fixes #<xyz>.)

(or if this PR is one task of a github issue, please add Master Issue: #<xyz> to link to the master issue.)

Master Issue: #

Motivation

  • Operational data structure for tracking resource groups
  • CRUD operations for these structures
  • tenant/namespace operations to register/unregister usage to resource groups
  • periodic gathering of resource usage into these data structures
  • calculation of quota for the next while based on usage of all brokers

Modifications

  • added code and unit tests for the above

Verifying this change

  • Make sure that the change passes the CI checks.

    • Added unit tests for
    • ops on resource-groups
    • quota-calculation
    • data-usage recording for resource groups

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

If yes was chosen, please highlight the changes

  • Dependencies (does it add or upgrade a dependency): no
  • The public API: no
  • The schema: no
  • The default values of configurations: no
  • The wire protocol: no
  • The rest endpoints: no
  • The admin cli options: no
  • Anything that affects deployment: no

Documentation

This code is a part of a set of PRs which will together stand up a new feature (resource-groups) in Pulsar. WIP.

  • Does this pull request introduce a new feature? (yes / no)
  • If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
  • If a feature is not applicable for documentation, explain why?
  • If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

@kaushik-develop
Copy link
Contributor Author

/pulsarbot run-failure-checks

@sijie sijie added this to the 2.8.0 milestone Apr 13, 2021
@kaushik-develop
Copy link
Contributor Author

/pulsarbot run-failure-checks

@merlimat merlimat requested a review from jerrypeng April 14, 2021 16:45
@kaushik-develop
Copy link
Contributor Author

/pulsarbot run-failure-checks

2 similar comments
@kaushik-develop
Copy link
Contributor Author

/pulsarbot run-failure-checks

@kaushik-develop
Copy link
Contributor Author

/pulsarbot run-failure-checks

@merlimat merlimat added the type/feature The PR added a new feature or issue requested a new feature label Apr 16, 2021
@merlimat merlimat merged commit b614448 into apache:master Apr 16, 2021
@kaushik-develop kaushik-develop deleted the push_rg_usage_to_oss branch April 16, 2021 01:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/broker type/feature The PR added a new feature or issue requested a new feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants