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

[docs] Add FAQ #1927

Merged
merged 6 commits into from
Sep 13, 2019
Merged

[docs] Add FAQ #1927

merged 6 commits into from
Sep 13, 2019

Conversation

benraskin92
Copy link
Collaborator

What this PR does / why we need it:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing and/or backwards incompatible change?:


Does this PR require updating code package or user-facing documentation?:


@@ -1 +1,70 @@
# FAQs

- **Is there a way to disable M3DB embedded `etcd` and just use an external `etcd` cluster?**
Yes, you can definitely do that. It's all just about setting the etcd endpoints in config as etcd hosts instead of M3DB hosts.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Link to how to set up external etcd cluster perhaps?

Refer to the [troubleshooting guide](../troubleshooting/index.md).

- **Do you support PromQL?**
Yes, M3Query and M3Coordinator both support PromQL.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Shall we mention support for Graphite too?

Yes, M3Query and M3Coordinator both support PromQL.

- **Does M3DB store both data and (tag) metadata on the same node?**
Yes it stores the data as well as the tags since it has an embedded index. Make sure you have `IndexEnabled` set to `true` in your namespace configuration
Copy link
Collaborator

Choose a reason for hiding this comment

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

When you say data, maybe clarify with time series datapoints?

If you’re adding namespaces, the m3dbnode process will pickup the new namespace without a restart.

- **Do I need to restart M3DB if I change or delete a namespace?**
If you’re removing or modifying an existing namespace, you’ll need to restart the m3dbnode process. It is recommended to restart one node at a time and wait for a node to be completely bootstrapped before restarting another node.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Hmm, that can technically continue on and keep using the cluster right? Maybe change wording to complete the namespace deletion process?

Refer to the [Aggregation section](../how_to/query) of the M3Query how-to guide.

- **How do I set up aggregation using a separate aggregation tier?**
<Fill this in>
Copy link
Collaborator

Choose a reason for hiding this comment

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

??

See the `Ticking` graph on [M3DB dashboard](https://grafana.com/dashboards/8126).

- **How much memory utilization should I run M3DB at?**
We recommend not going above 40%.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Hmm, is that very aggressive? maybe 50%?

@benraskin92 benraskin92 changed the title [docs] [WIP] Add FAQ [docs] Add FAQ Sep 12, 2019
@codecov
Copy link

codecov bot commented Sep 12, 2019

Codecov Report

Merging #1927 into master will increase coverage by 3.4%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##           master    #1927     +/-   ##
=========================================
+ Coverage    59.9%    63.4%   +3.4%     
=========================================
  Files        1085     1113     +28     
  Lines      102830   104790   +1960     
=========================================
+ Hits        61677    66467   +4790     
+ Misses      36906    34077   -2829     
+ Partials     4247     4246      -1
Flag Coverage Δ
#aggregator 79.8% <ø> (ø) ⬆️
#cluster 56.2% <ø> (+11.5%) ⬆️
#collector 63.7% <ø> (ø) ⬆️
#dbnode 64.8% <ø> (+3.2%) ⬆️
#m3em 59.6% <ø> (-8.9%) ⬇️
#m3ninx 61.1% <ø> (+4.3%) ⬆️
#m3nsch 51.1% <ø> (ø) ⬆️
#metrics 17.7% <ø> (ø) ⬆️
#msg 74.9% <ø> (+0.1%) ⬆️
#query 68.1% <ø> (+0.1%) ⬆️
#x 75.2% <ø> (+21.5%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 80377b0...8ff4aad. Read the comment docs.

Copy link
Collaborator

@martin-mao martin-mao left a comment

Choose a reason for hiding this comment

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

Left a couple of comments, but mostly LGTM.

See [M3DB openhttps://m3db.io/openapi

- **What is the recommended way to upgrade my M3 stack?**
<Fill this in>
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can we change this to TBA?

We recommend not going above 50%.

- **What is the recommended hardware to run on?**
<Fill this in>
Copy link
Collaborator

Choose a reason for hiding this comment

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

Same here.

@benraskin92 benraskin92 merged commit 1ac51c4 into master Sep 13, 2019
@benraskin92 benraskin92 deleted the braskin/add_faq branch September 13, 2019 00:42
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.

2 participants