From 73c545fb0aebc47b315d9b7c912ce23d3ff965ba Mon Sep 17 00:00:00 2001 From: Hendrik Muhs Date: Wed, 16 Oct 2019 11:48:03 +0200 Subject: [PATCH 1/6] document limitation regarding rolling upgrade with 7.2, 7.3 --- docs/reference/transform/limitations.asciidoc | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/docs/reference/transform/limitations.asciidoc b/docs/reference/transform/limitations.asciidoc index 1d3d38c943691..d79eff8c94bb1 100644 --- a/docs/reference/transform/limitations.asciidoc +++ b/docs/reference/transform/limitations.asciidoc @@ -33,6 +33,14 @@ upgrade from 7.2 to a newer version, and {transforms} have been created in 7.2, the {transforms} UI (earler {dataframe} UI) will not work. Please wait until all nodes have been upgraded to the newer version before using the {transforms} UI. +[float] +[[transform-rolling-upgrade-limitation]] +==== {transforms-cap} Transforms suspended during a rolling upgrade from 7.2 and 7.3 + +If your cluster contains mixed version nodes, for example during a rolling +upgrade from 7.2, 7.3 to a newer version, transforms are suspended for the time of +the upgrade. Once the upgrade is done, transforms will resume automatically, there is +no action required. [float] [[transform-datatype-limitations]] @@ -181,9 +189,9 @@ for the {transform} checkpoint to complete. [float] [[transform-scheduling-limitations]] -==== {cdataframe-cap} scheduling limitations +==== {ctransform-cap} scheduling limitations -A {cdataframe} periodically checks for changes to source data. The functionality +A {ctransform} periodically checks for changes to source data. The functionality of the scheduler is currently limited to a basic periodic timer which can be within the `frequency` range from 1s to 1h. The default is 1m. This is designed to run little and often. When choosing a `frequency` for this timer consider @@ -206,7 +214,7 @@ When using the API to delete a failed {transform}, first stop it using [float] [[transform-availability-limitations]] -==== {cdataframes-cap} may give incorrect results if documents are not yet available to search +==== {ctransforms-cap} may give incorrect results if documents are not yet available to search After a document is indexed, there is a very small delay until it is available to search. From a2a33a7c014a94f94c703487193b9a1922e90c05 Mon Sep 17 00:00:00 2001 From: Hendrik Muhs Date: Wed, 16 Oct 2019 14:00:17 +0200 Subject: [PATCH 2/6] clarify that only reassignment is affected --- docs/reference/transform/limitations.asciidoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/reference/transform/limitations.asciidoc b/docs/reference/transform/limitations.asciidoc index d79eff8c94bb1..eaa18c79c8ced 100644 --- a/docs/reference/transform/limitations.asciidoc +++ b/docs/reference/transform/limitations.asciidoc @@ -35,12 +35,12 @@ nodes have been upgraded to the newer version before using the {transforms} UI. [float] [[transform-rolling-upgrade-limitation]] -==== {transforms-cap} Transforms suspended during a rolling upgrade from 7.2 and 7.3 +==== {transforms-cap} Transforms reassignment suspended during a rolling upgrade from 7.2 and 7.3 If your cluster contains mixed version nodes, for example during a rolling -upgrade from 7.2, 7.3 to a newer version, transforms are suspended for the time of -the upgrade. Once the upgrade is done, transforms will resume automatically, there is -no action required. +upgrade from 7.2, 7.3 to a newer version, transforms whose nodes are stopped will +not be reassigned until the upgrade is complete. Once the upgrade is done, transforms +will resume automatically, there is no action required. [float] [[transform-datatype-limitations]] From 398937749335ea6e94a67b0e3ac4bfae96241c99 Mon Sep 17 00:00:00 2001 From: Hendrik Muhs Date: Fri, 18 Oct 2019 13:30:22 +0200 Subject: [PATCH 3/6] Update docs/reference/transform/limitations.asciidoc Co-Authored-By: Lisa Cawley --- docs/reference/transform/limitations.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/transform/limitations.asciidoc b/docs/reference/transform/limitations.asciidoc index eaa18c79c8ced..0f11d4fe8f7f2 100644 --- a/docs/reference/transform/limitations.asciidoc +++ b/docs/reference/transform/limitations.asciidoc @@ -39,7 +39,7 @@ nodes have been upgraded to the newer version before using the {transforms} UI. If your cluster contains mixed version nodes, for example during a rolling upgrade from 7.2, 7.3 to a newer version, transforms whose nodes are stopped will -not be reassigned until the upgrade is complete. Once the upgrade is done, transforms +not be reassigned until the upgrade is complete. After the upgrade is done, {transforms} will resume automatically, there is no action required. [float] From 3dbb5b2455ff8fa94d3b8810ac1230d46f10643f Mon Sep 17 00:00:00 2001 From: Hendrik Muhs Date: Fri, 18 Oct 2019 13:30:29 +0200 Subject: [PATCH 4/6] Update docs/reference/transform/limitations.asciidoc Co-Authored-By: Lisa Cawley --- docs/reference/transform/limitations.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/transform/limitations.asciidoc b/docs/reference/transform/limitations.asciidoc index 0f11d4fe8f7f2..0c1379d199365 100644 --- a/docs/reference/transform/limitations.asciidoc +++ b/docs/reference/transform/limitations.asciidoc @@ -40,7 +40,7 @@ nodes have been upgraded to the newer version before using the {transforms} UI. If your cluster contains mixed version nodes, for example during a rolling upgrade from 7.2, 7.3 to a newer version, transforms whose nodes are stopped will not be reassigned until the upgrade is complete. After the upgrade is done, {transforms} -will resume automatically, there is no action required. +resume automatically; no action is required. [float] [[transform-datatype-limitations]] From 8ea8fdf8110911dbe2e8ccbd29bffa8a0adca0a3 Mon Sep 17 00:00:00 2001 From: Hendrik Muhs Date: Fri, 18 Oct 2019 13:30:38 +0200 Subject: [PATCH 5/6] Update docs/reference/transform/limitations.asciidoc Co-Authored-By: Lisa Cawley --- docs/reference/transform/limitations.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/transform/limitations.asciidoc b/docs/reference/transform/limitations.asciidoc index 0c1379d199365..bd1092bcd2904 100644 --- a/docs/reference/transform/limitations.asciidoc +++ b/docs/reference/transform/limitations.asciidoc @@ -35,7 +35,7 @@ nodes have been upgraded to the newer version before using the {transforms} UI. [float] [[transform-rolling-upgrade-limitation]] -==== {transforms-cap} Transforms reassignment suspended during a rolling upgrade from 7.2 and 7.3 +==== {transforms-cap} reassignment suspended during a rolling upgrade from 7.2 and 7.3 If your cluster contains mixed version nodes, for example during a rolling upgrade from 7.2, 7.3 to a newer version, transforms whose nodes are stopped will From 654efdc3aa11dd990f06ddf0cea3a199c9afb054 Mon Sep 17 00:00:00 2001 From: Hendrik Muhs Date: Mon, 21 Oct 2019 08:09:01 +0200 Subject: [PATCH 6/6] Update limitations.asciidoc --- docs/reference/transform/limitations.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/transform/limitations.asciidoc b/docs/reference/transform/limitations.asciidoc index bd1092bcd2904..463f66f24e3e5 100644 --- a/docs/reference/transform/limitations.asciidoc +++ b/docs/reference/transform/limitations.asciidoc @@ -38,7 +38,7 @@ nodes have been upgraded to the newer version before using the {transforms} UI. ==== {transforms-cap} reassignment suspended during a rolling upgrade from 7.2 and 7.3 If your cluster contains mixed version nodes, for example during a rolling -upgrade from 7.2, 7.3 to a newer version, transforms whose nodes are stopped will +upgrade from 7.2 or 7.3 to a newer version, {transforms} whose nodes are stopped will not be reassigned until the upgrade is complete. After the upgrade is done, {transforms} resume automatically; no action is required.