-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Trivial - P5
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
-
Fully Compatible
-
DAG 2020-01-13, DAG 2020-01-27
-
2
detect_outliers should be running in system_perfl.yml.
But because it doesn't set -o verbose, we can't see if it runs or not:
[2019/12/12 16:36:31.301] # detect outliers needs to run, so defer the post_run_check exit status to later [2019/12/12 16:36:31.301] echo $? > post_run_check.status [2019/12/12 16:36:31.302] Running command 'shell.exec' in "analyze" (step 4.3 of 4) [2019/12/12 16:36:31.305] Running command 'shell.exec' in "analyze" (step 4.4 of 4) [2019/12/12 16:36:31.306] filename=rejects.json [2019/12/12 16:36:31.306] if [ -s "$filename" ]; then [2019/12/12 16:36:31.306] echo "Rejecting task due to the following outliers:" [2019/12/12 16:36:31.306] cat "$filename"
See step 4.4 of 4.
Also the artifact doesn't contain a detect_outliers.log.
Finally, there have been no outliers saved in the outliers collection for some time:
MongoDB Enterprise PerformanceData-shard-0:PRIMARY> db.outliers.find({"project" : "sys-perf"}).sort({_id:-1}).limit(1)[0]._id.getTimestamp()
ISODate("2019-11-11T12:19:07Z")