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

Optionally gather mongodb cluster status #7515

Merged
merged 1 commit into from
May 22, 2020
Merged

Optionally gather mongodb cluster status #7515

merged 1 commit into from
May 22, 2020

Conversation

raul-te
Copy link
Contributor

@raul-te raul-te commented May 15, 2020

It can be expensive to compute these metrics. In particular, when
retrieving the amount of jumbo chunks, an index is not being used and
consequently the query triggers an expensive COLLSCAN. For big
databases, this query has negative impact on the cluster performance.

I left the default value of gather_cluster_status to true so as not to break
the current behavior.

Required for all PRs:

  • Signed CLA.
  • Associated README.md updated.
  • Has appropriate unit tests.

It can be expensive to compute these metrics. In particular, when
retrieveing the amount of jumbo chunks, an index is not being used and
consequently the query triggers an expensive COLLSCAN. For big
databases, this query has negative impact on the cluster performance.
@danielnelson danielnelson added area/mongodb feat Improvement on an existing feature such as adding a new setting/mode to an existing plugin performance problems with decreased performance or enhancements that improve performance labels May 22, 2020
@danielnelson danielnelson added this to the 1.15.0 milestone May 22, 2020
@danielnelson danielnelson merged commit 4d071be into influxdata:master May 22, 2020
rhajek pushed a commit to bonitoo-io/telegraf that referenced this pull request Jul 13, 2020
It can be expensive to compute these metrics. In particular, when
retrieveing the amount of jumbo chunks, an index is not being used and
consequently the query triggers an expensive COLLSCAN. For big
databases, this query has negative impact on the cluster performance.
idohalevi pushed a commit to idohalevi/telegraf that referenced this pull request Sep 29, 2020
It can be expensive to compute these metrics. In particular, when
retrieveing the amount of jumbo chunks, an index is not being used and
consequently the query triggers an expensive COLLSCAN. For big
databases, this query has negative impact on the cluster performance.
arstercz pushed a commit to arstercz/telegraf that referenced this pull request Mar 5, 2023
It can be expensive to compute these metrics. In particular, when
retrieveing the amount of jumbo chunks, an index is not being used and
consequently the query triggers an expensive COLLSCAN. For big
databases, this query has negative impact on the cluster performance.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/mongodb feat Improvement on an existing feature such as adding a new setting/mode to an existing plugin performance problems with decreased performance or enhancements that improve performance
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants