From e0ba3bbebaeb0e77054de920ce494a674b23d599 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Fri, 17 Apr 2020 14:26:54 +1000
Subject: [PATCH] Allow forcemerge in the hot phase for ILM policies (#4598)
 (#4625)

Co-authored-by: Stuart Cam <stuart.cam@elastic.co>
---
 src/Nest/XPack/Ilm/Actions/ForceMergeAction.cs | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/src/Nest/XPack/Ilm/Actions/ForceMergeAction.cs b/src/Nest/XPack/Ilm/Actions/ForceMergeAction.cs
index fb9881b99ea..ad1f7f9dc40 100644
--- a/src/Nest/XPack/Ilm/Actions/ForceMergeAction.cs
+++ b/src/Nest/XPack/Ilm/Actions/ForceMergeAction.cs
@@ -6,7 +6,10 @@ namespace Nest
 	/// The Force Merge Action force merges the index into at most a specific number of segments.
 	/// </summary>
 	/// <remarks>
-	/// Phases allowed: warm.
+	/// Phases allowed: hot, warm.
+	///
+	/// NOTE: If the action is used in the `hot` phase, the `rollover` action *must* be present.
+	/// ILM validates this predicate and will refuse a policy with a forcemerge in the hot phase without a rollover action.
 	/// </remarks>
 	public interface IForceMergeLifecycleAction : ILifecycleAction
 	{