From 611c4401f8fe6444a89656b506de9ea86e438c41 Mon Sep 17 00:00:00 2001
From: Aliaksandr Valialkin <valyala@gmail.com>
Date: Wed, 12 Jun 2019 21:30:36 +0300
Subject: [PATCH] README.md: mention about multi-tenancy

---
 README.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/README.md b/README.md
index ec3ec2f23..e8e08caeb 100644
--- a/README.md
+++ b/README.md
@@ -75,6 +75,7 @@ Cluster version is available [here](https://github.com/VictoriaMetrics/VictoriaM
   - [High availability](#high-availability)
   - [Multiple retentions](#multiple-retentions)
   - [Downsampling](#downsampling)
+  - [Multi-tenancy](#multi-tenancy)
   - [Scalability and cluster version](#scalability-and-cluster-version)
   - [Security](#security)
   - [Tuning](#tuning)
@@ -444,6 +445,11 @@ These properties reduce the need in downsampling. We plan implementing downsampl
 See [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/36) for details.
 
 
+### Multi-tenancy
+
+Single-node VictoriaMetrics doesn't support multi-tenancy. Use [cluster version](https://github.com/VictoriaMetrics/VictoriaMetrics/tree/cluster) instead.
+
+
 ### Scalability and cluster version
 
 Though single-node VictoriaMetrics cannot scale to multiple nodes, it is optimized for resource usage - storage size / bandwidth / IOPS, RAM, CPU.