proposal
proposal copied to clipboard
m3db
M3 Design Documents
We are planning to move M3 to arm based machine. Currently, M3 supports amd based machine. We are thinking to update the Dockerfile and Makefile to support arm. Please let...
M3 depends on mid-2018 forks of the various prometheus/client_golang -related projects (which appear to have no modifications). The principle reason is to make it so M3, and projects dependent on...
Design doc: https://docs.google.com/document/d/17vsyICvakH1RvEkhuYYENg06e6SpdAeXgYMsp5V2k2s/edit#
Implementation pending, algorithm: 1. During cold flush, for any series added to the volume, add to an index segment the series (load existing "cold writes index segment" from disk into...
Even though M3DB achieves great compression (10x compression of timestamp/float in the cluster I will be describing below) some of our clusters that retain data for 40 days are still...
M3DB currently does not have any form of background repairs. This means that unless a manual repair is triggered (stop a node, delete all the data, then turn it back...
Doc: https://docs.google.com/document/d/1p9xvjGTiUhzPe1BsNtj6jzP5fX9lB1miPdp1t_Ov8L8/edit#heading=h.odx5s24ea0wm
Let me know if you feel this warrants a design doc, but this proposal is to allow using the arbitrary out of order writes code path to merge snapshots together...
This issue propose to add schema management to M3DB as part of M3DB's effort to support complex type values. The proposal will discuss schema definition language, schema evolution, storage, deployment,...
# Problem This proposal addresses the following problems: ## Part 1. Bootstrapping generates large volumes of commit logs During bootstrapping nodes generate large volumes of commit logs that cannot be...