8000 [DOCS] Add warning to changing blocksize by ChrisChinchilla · Pull Request #3096 · m3db/m3 · GitHub
[go: up one dir, main page]

Skip to content

[DOCS] Add warning to changing blocksize - #3096

Merged
ChrisChinchilla merged 4 commits into
masterfrom
chrischinch/blocksize-warn
Jan 21, 2021
Merged

ChrisChinchilla merged 4 commits into
masterfrom
chrischinch/blocksize-warn

Conversation

@ChrisChinchilla
Copy link
Copy Markdown
Contributor

As noted in #2789 (comment) this PR adds a warning to highlight users shouldn't change blocksize.

Signed-off-by: ChrisChinchilla <chris@chronosphere.io>
@codecov
codecov Bot commented Jan 18, 2021 •
Copy link
Copy Markdown

Codecov Report

Merging #3096 (2fe3521) into master (2d68fad) will increase coverage by 6.7%.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff            @@
##           master   #3096     +/-   ##
========================================
+ Coverage    65.5%   72.3%   +6.7%     
========================================
  Files        1080    1083      +3     
  Lines       99058   99893    +835     
========================================
+ Hits        64906   72231   +7325     
+ Misses      29367   22631   -6736     
- Partials     4785    5031    +246     
Flag Coverage Δ
aggregator 75.9% <ø> (+7.5%) ⬆️
cluster 84.8% <ø> (+18.2%) ⬆️
collector 84.3% <ø> (ø)
dbnode 78.7% <ø> (+3.0%) ⬆️
m3em 74.4% <ø> (+16.2%) ⬆️
m3ninx 73.1% <ø> (+8.3%) ⬆️
metrics 20.0% <ø> (ø)
msg 73.7% <ø> (-0.4%) ⬇️
query 67.4% <ø> (+10.6%) ⬆️
x 80.2% <ø> (+12.8%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.


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 2d68fad...f876f3e. Read the comment docs.

There is currently no atomic namespace modification endpoint. Instead, you will need to delete a namespace and then add it back again with the same name, but modified settings. Review the individual namespace settings above to determine whether or not a given setting is safe to modify.

{{% notice warning %}}
For example, it is never safe to modify the blockSize of a namespace.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

maybe we should phrase this as a list of warnings / unsafe items, with this being the first?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@wesleyk Good idea, but I think I'll do that when we get to the rewrite, which is kind of in progress right now anyway

@ChrisChinchilla
ChrisChinchilla merged commit 7ae7b3c into master Jan 21, 2021
@ChrisChinchilla
ChrisChinchilla deleted the chrischinch/blocksize-warn branch January 21, 2021 16:23
soundvibe pushed a commit that referenced this pull request Jan 22, 2021
* master:
  [DOCS] Update to cluster docs (#3084)
  [dbnode][coordinator] Ensure docs limit is propagated for search and aggregate RPCs (#3108)
  [query] Take bounds into account for list endpoints (#3110)
  Add warning to changing blocksize (#3096)
  Add support for dynamic query limit overriding (#3090)
  [tests] test setups exported to allow us to use it from other packages (#3042)
  [query] Implemented Graphite's pow function (#3048)
  [dbnode] Direct conversion of encoded tags to doc.Metadata (#3087)
  [tests] Skip flaky TestWatchNoLeader (#3106)
  [dbnode] Faster search of tag bytes in convert.FromSeriesIDAndTags (#3075)
  Replace bytes.Compare() == 0 with bytes.Equal() (#3101)
  Capture seekerMgr instead Rlock (#3104)
  [m3db] Check bloom filter before stream request allocation (#3103)
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

0