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.

Sign up for GitHub

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] Tiny spelling mistake fix in FAQ #2448

Merged
merged 6 commits into from
Aug 6, 2020
Merged

[docs] Tiny spelling mistake fix in FAQ #2448

Changes from 5 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
04a285d
Tiny spelling mistake fix in FAQ
asafm Jul 7, 2020
1020ca8
Merge branch 'master' into patch-2
asafm Jul 9, 2020
c29eb22
Merge branch 'master' into patch-2
asafm Jul 11, 2020
09ce009
Merge branch 'master' into patch-2
asafm Jul 20, 2020
fd03037
Merge branch 'master' into patch-2
benraskin92 Aug 5, 2020
fa2f331
Merge branch 'master' into patch-2
benraskin92 Aug 6, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/faqs/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ Yes it stores the data (i.e. the timeseries datapoints) as well as the tags sinc

- **How are writes handled and how is the data kept consistent within M3DB?**
M3 uses quorum/majority consistency to ensure data is written to replicas in a way that can be read back consistently.
For example, if you have a replication factor of 3 and your set your write and read consistencies to quorum, then all writes will only succeed if they make it to at least 2 of the 3 replicas, and reads will only succeed if they get results back from at least 2 of the 3 replicas
For example, if you have a replication factor of 3 and you set your write and read consistencies to quorum, then all writes will only succeed if they make it to at least 2 of the 3 replicas, and reads will only succeed if they get results back from at least 2 of the 3 replicas

- **Do I need to restart M3DB if I add a namespace?**
If you’re adding namespaces, the m3dbnode process will pickup the new namespace without a restart.
Expand Down Expand Up @@ -73,4 +73,4 @@ TBA
Refer to the [Namespace configuration guide](../operational_guide/namespace_configuration.md).

- **How can I see the cardinality of my metrics?**
Currently, the best way is to go to the [M3DB Node Details Dashboard](https://grafana.com/grafana/dashboards/8126) and look at the `Ticking` panel. However, this is not entirely accurate because of the way data is stored in M3DB -- time series are stored inside time-based blocks that you configure. In actuality, the `Ticking` graph shows you how many unique series there are for the most recent block that has persisted. In the future, we plan to introduce easier ways to determine the number of unique time series.
Currently, the best way is to go to the [M3DB Node Details Dashboard](https://grafana.com/grafana/dashboards/8126) and look at the `Ticking` panel. However, this is not entirely accurate because of the way data is stored in M3DB -- time series are stored inside time-based blocks that you configure. In actuality, the `Ticking` graph shows you how many unique series there are for the most recent block that has persisted. In the future, we plan to introduce easier ways to determine the number of unique time series.