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

Apply aiven specific patches on top of upstream 1.2.0 #13

Merged
merged 11 commits into from
Dec 8, 2021

Conversation

tsharju
Copy link

@tsharju tsharju commented Sep 23, 2021

This PR takes our custom patches and applies them on top of M3 1.2.0 to a new release branch aiven-1.2.

tsharju and others added 11 commits September 21, 2021 10:14
- Add environment variable to configure default pool size.

  Not to be upstreamed, upstream SHOULD provide configuration for all
  pools but currently there's hardcoded default sized pools for
  e.g. tag{de,en}coders and some other places. With this default, we
  can change it from 4096 to something else as we wish.

- Add environment variable with (optional) pool size whitelist.

  Even with default pool size changed to e.g. 4096->64, lots of large
  pools are still either hardcoded in codebase, or in configuration
  defaults.
@ryansammonaiven
Copy link

ryansammonaiven commented Nov 18, 2021

@tsharju Are we still planning on updating from upstream in the near future? The M3 team is planning to cut v1.4.0 soon, which will include a change that I made that will fix an error we encountered when Vmalert uses M3 as its data source (last_over_time is not supported, PR, JIRA). If we could prepare an Aiven-patched v1.4.0 when it is available, it would be helpful for our alerting solutions.

@tsharju
Copy link
Author

tsharju commented Nov 19, 2021

@ryansammonaiven Sure, I decided to leave 1.3.0 not updated as it mainly contained patches I made that are already in our patched 1.2.0 version. But once 1.4.0 becomes available I believe we'll try to get that available asap.

@tsharju tsharju merged commit 6f0afa2 into aiven-1.2 Dec 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants