From 711ee1e8d4a0d26e4cdef29e74ddc49d90c61182 Mon Sep 17 00:00:00 2001 From: Lisa Cawley Date: Thu, 11 May 2017 09:21:08 -0700 Subject: [PATCH] [DOCS] Add FAQ for ML rolling upgrade issue (elastic/x-pack-elasticsearch#1390) * [DOCS] Add FAQ for ML rolling upgrade issue * [DOCS] More info for ML rolling upgrade issue Original commit: elastic/x-pack-elasticsearch@be195477b0ff4f2b173dce67db8c165724a34417 --- docs/en/ml/troubleshooting.asciidoc | 33 +++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) create mode 100644 docs/en/ml/troubleshooting.asciidoc diff --git a/docs/en/ml/troubleshooting.asciidoc b/docs/en/ml/troubleshooting.asciidoc new file mode 100644 index 00000000000..68f8b90c015 --- /dev/null +++ b/docs/en/ml/troubleshooting.asciidoc @@ -0,0 +1,33 @@ +[[ml-troubleshooting]] +== {xpackml} Troubleshooting + +Use the information in this section to troubleshoot common problems and find +answers for frequently asked questions. + +To get help, see <>. + +[float] +[[ml-rollingupgrade]] +=== Machine learning features unavailable after rolling upgrade + +This problem occurs after you upgrade all of the nodes in your cluster to +{version} by using rolling upgrades. When you try to use {xpackml} features for +the first time, all attempts fail, though `GET _xpack` and `GET _xpack/usage` +indicate that {xpack} is enabled. + +*Symptoms:* + +* Errors when you click *Machine Learning* in {kib}. +For example: `Jobs list could not be created` and `An internal server error occurred`. +* Null pointer and remote transport exceptions when you run {ml} APIs such as +`GET _xpack/ml/anomaly_detectors` and `GET _xpack/ml/datafeeds`. +* Errors in the log files on the master nodes. +For example: `unable to install ml metadata upon startup` + +*Resolution:* + +After you upgrade all master-eligible nodes to {es} {version} and {xpack} +{version}, restart the current master node, which triggers the {xpackml} +features to re-initialize. + +For more information, see {ref}/rolling-upgrades.html[Rolling upgrades].