From 8596c2bad5b28bc8c84f47421026dfed26054dc4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ji=C5=99=C3=AD=20Programagor?= <programagor@gmail.com>
Date: Fri, 14 Sep 2018 12:42:35 +0200
Subject: [PATCH] Fixes #23179

Issue #23179 was caused by ignoring multiple replicas of the same shard, even if they are on different nodes. This commit fixes that.
---
 .../server/lib/elasticsearch/shards/get_shard_allocation.js     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/x-pack/plugins/monitoring/server/lib/elasticsearch/shards/get_shard_allocation.js b/x-pack/plugins/monitoring/server/lib/elasticsearch/shards/get_shard_allocation.js
index e39e1181c5ed2..4e75115a48412 100644
--- a/x-pack/plugins/monitoring/server/lib/elasticsearch/shards/get_shard_allocation.js
+++ b/x-pack/plugins/monitoring/server/lib/elasticsearch/shards/get_shard_allocation.js
@@ -24,7 +24,7 @@ export function handleResponse(response) {
 
     if (shard) {
       // note: if the request is for a node, then it's enough to deduplicate without primary, but for indices it displays both
-      const shardId = `${shard.index}-${shard.shard}-${shard.primary}-${shard.relocating_node}`;
+      const shardId = `${shard.index}-${shard.shard}-${shard.primary}-${shard.relocating_node}-${shard.node}`;
 
       if (!uniqueShards.has(shardId)) {
         shards.push(shard);