From aa4fb29adacd3c78b163071978d57aa35e2976af Mon Sep 17 00:00:00 2001 From: Luke Elmers Date: Mon, 28 Jun 2021 12:55:22 -0600 Subject: [PATCH] Convert image names to snake_case in RFC 0020. --- .../cluster_mode.png} | Bin .../no_cluster_mode.png} | Bin .../perf_4_workers.png} | Bin .../perf_clustering_2_worker.png} | Bin .../perf_no_clustering.png} | Bin rfcs/text/0020_nodejs_clustering.md | 10 +++++----- 6 files changed, 5 insertions(+), 5 deletions(-) rename rfcs/images/{15_clustering/cluster-mode.png => 20_clustering/cluster_mode.png} (100%) rename rfcs/images/{15_clustering/no-cluster-mode.png => 20_clustering/no_cluster_mode.png} (100%) rename rfcs/images/{15_clustering/perf-4-workers.png => 20_clustering/perf_4_workers.png} (100%) rename rfcs/images/{15_clustering/perf-clustering-2-worker.png => 20_clustering/perf_clustering_2_worker.png} (100%) rename rfcs/images/{15_clustering/perf-no-clustering.png => 20_clustering/perf_no_clustering.png} (100%) diff --git a/rfcs/images/15_clustering/cluster-mode.png b/rfcs/images/20_clustering/cluster_mode.png similarity index 100% rename from rfcs/images/15_clustering/cluster-mode.png rename to rfcs/images/20_clustering/cluster_mode.png diff --git a/rfcs/images/15_clustering/no-cluster-mode.png b/rfcs/images/20_clustering/no_cluster_mode.png similarity index 100% rename from rfcs/images/15_clustering/no-cluster-mode.png rename to rfcs/images/20_clustering/no_cluster_mode.png diff --git a/rfcs/images/15_clustering/perf-4-workers.png b/rfcs/images/20_clustering/perf_4_workers.png similarity index 100% rename from rfcs/images/15_clustering/perf-4-workers.png rename to rfcs/images/20_clustering/perf_4_workers.png diff --git a/rfcs/images/15_clustering/perf-clustering-2-worker.png b/rfcs/images/20_clustering/perf_clustering_2_worker.png similarity index 100% rename from rfcs/images/15_clustering/perf-clustering-2-worker.png rename to rfcs/images/20_clustering/perf_clustering_2_worker.png diff --git a/rfcs/images/15_clustering/perf-no-clustering.png b/rfcs/images/20_clustering/perf_no_clustering.png similarity index 100% rename from rfcs/images/15_clustering/perf-no-clustering.png rename to rfcs/images/20_clustering/perf_no_clustering.png diff --git a/rfcs/text/0020_nodejs_clustering.md b/rfcs/text/0020_nodejs_clustering.md index 62c4de4d3cbe4..9ee5d764c8de1 100644 --- a/rfcs/text/0020_nodejs_clustering.md +++ b/rfcs/text/0020_nodejs_clustering.md @@ -59,14 +59,14 @@ container per host CPU with a single Kibana process per container). In 'classic' mode, the Kibana server is started in the main Node.js process. -![image](../images/15_clustering/no-cluster-mode.png) +![image](../images/20_clustering/no_cluster_mode.png) In clustering mode, the main Node.js process would only start the coordinator, which would then fork workers using Node's `cluster` API. Node's underlying socket implementation allows multiple processes to listen to the same ports, effectively performing http traffic balancing between the workers for us. -![image](../images/15_clustering/cluster-mode.png) +![image](../images/20_clustering/cluster_mode.png) The coordinator's primary responsibility is to orchestrate the workers. It would not be a 'super' worker handling both the job of a worker while being in charge of managing the other workers. @@ -97,15 +97,15 @@ Intel Core i9 - 32 GB 2400 MHz DDR4), using the default configuration of the `ki #### Non-clustered mode -![image](../images/15_clustering/perf-no-clustering.png) +![image](../images/20_clustering/perf_no_clustering.png) #### Clustered mode, 2 workers -![image](../images/15_clustering/perf-clustering-2-worker.png) +![image](../images/20_clustering/perf_clustering_2_worker.png) #### Clustered mode, 4 workers -![image](../images/15_clustering/perf-4-workers.png) +![image](../images/20_clustering/perf_4_workers.png) ### 4.1.2 Analysis