Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOCS][Transform] document limitation regarding rolling upgrade with 7.2, 7.3 #48118

Merged
merged 6 commits into from
Oct 22, 2019
Merged

[DOCS][Transform] document limitation regarding rolling upgrade with 7.2, 7.3 #48118

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
73c545f
document limitation regarding rolling upgrade with 7.2, 7.3
Oct 16, 2019
a2a33a7
clarify that only reassignment is affected
Oct 16, 2019
3989377
Update docs/reference/transform/limitations.asciidoc
Oct 18, 2019
3dbb5b2
Update docs/reference/transform/limitations.asciidoc
Oct 18, 2019
8ea8fdf
Update docs/reference/transform/limitations.asciidoc
Oct 18, 2019
654efdc
Update limitations.asciidoc
Oct 21, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 11 additions & 3 deletions docs/reference/transform/limitations.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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} 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 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.

[float]
[[transform-datatype-limitations]]
Expand Down Expand Up @@ -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
Expand All @@ -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.
Expand Down