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

BugFix#18543 maxSize and segment max cache size is not pass (right now is using the default value) #245

Closed
wants to merge 12 commits into from

Conversation

rgomezborder
Copy link
Member

@rgomezborder rgomezborder commented Nov 9, 2024

Related issue in RedMine

Description

  • Updating and improving harddisk_services method.
  • Passing druid_historical hd_service maxsize variable to coobook-druid.

Details

  • harddisk_services method handles 4 differents services. Before of this PR this was the result of it.
"hd_services_current": {
  "kafka": 0.0,
  "zookeeper": 0.0,
  "riak": 0.0,
  "druid_historical": 0.0
},

Now we retrieve the total size of the root device in bytes by converting the disk size from kilobytes to bytes. Then, for each service in node['redborder']['manager']['hd_services'], it calculates the number of bytes to allocate by multiplying the total disk size by service_count, which now represents the percentage of disk space allocated to that service.

This allocation is then stored in the hd_services hash, with each service's name as the key and its allocated size in bytes as the value.

Copy link

the-label-bot bot commented Nov 9, 2024

The Label Bot has predicted the following:

Category Value Confidence Applied Label

@rgomezborder rgomezborder deleted the bugfix/#18543_maxsize_is_not_pass branch November 12, 2024 11:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants