[ 
https://issues.apache.org/jira/browse/KUDU-3772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18102156#comment-18102156
 ] 

ASF subversion and git services commented on KUDU-3772:
-------------------------------------------------------

Commit df601446fbac5d3e75fecc05401311d5e8d83843 in kudu's branch 
refs/heads/master from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=df601446f ]

KUDU-3772 fix flakiness in MiniPrometheusTest.StartStopNoTargets

Before this fix, one of my RHEL9.6 x86_64 build/test machines would
regularly report a failure in the MiniPrometheusTest.StartStopNoTargets
scenario when running mini_prometheus-test.  Reports looked like below:

  src/kudu/util/mini_prometheus-test.cc:206: Failure
  Failed
  Bad status: Remote error: HTTP 503

This changelist address the issue.

I also tried a more generic approach, trying to rely on the documented
'/-/ready' URL [1] by running the readiness check right before returning
from the MiniPrometheus::Start() method.  However, it seems getting
HTTP 200 for GET/HEAD requests at the '/-/ready' URL doesn't guarantee
that Scrape/Target Manager initialization is complete, so the readiness
check is useless in this context.

[1] https://prometheus.io/docs/prometheus/latest/management_api/

Change-Id: I05e9ca3e3c8782e9b073dd2329846d5eac661dcf
Reviewed-on: http://gerrit.cloudera.org:8080/24658
Tested-by: Alexey Serbin <[email protected]>
Reviewed-by: Marton Greber <[email protected]>


> MiniPrometheusTest.StartStopNoTargets fails from time to time
> -------------------------------------------------------------
>
>                 Key: KUDU-3772
>                 URL: https://issues.apache.org/jira/browse/KUDU-3772
>             Project: Kudu
>          Issue Type: Bug
>          Components: test
>            Reporter: Alexey Serbin
>            Assignee: Alexey Serbin
>            Priority: Major
>         Attachments: mini_prometheus-test.20260709.txt.xz, 
> mini_prometheus-test.txt.xz, mp.tar.xz
>
>
> The newly introduced test scenario {{MiniPrometheusTest.StartStopNoTargets}} 
> from time to time fails on RHEL9.6 with the following message (DEBUG build):
> {noformat}
> rc/kudu/util/mini_prometheus-test.cc:129: Failure
> Failed
> Bad status: Remote error: HTTP 503
> {noformat}
> Full log and the test data directory contents tarball are attached.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to