16 Dec 2025 09:39:08 -0800 From: Sai Sanjay Reply-To: kube-burner/kube-burner To: kube-burner/kube-burner Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [kube-burner/kube-burner] [RFE]: Fork a process from kube-burner targetting combined workload execution (Issue #1041) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_6941993cb3f34_11911183338ed"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: sanjay7178 X-GitHub-Recipient: pfeifferj X-GitHub-Reason: subscribed List-ID: kube-burner/kube-burner List-Archive: https://github.com/kube-burner/kube-burner List-Post: List-Unsubscribe: , List-Unsubscribe-Post: List-Unsubscribe=One-Click X-GitHub-Notify-Platform: newsies X-GitHub-Labels: kind/enhancement X-GitHub-Assignees: X-GitHub-IssueState: open X-Auto-Response-Suppress: All destinations: github@josie.lol X-GitHub-Recipient-Address: github@josie.lol X-DKIM: signer='github.com' status='pass' reason='' DKIMCheck: Server passes DKIM test, 0 Spam score X-Spam-Score: 0.3 (/) X-Spam-Report: Spam detection software, running on the system "witcher.mxrouting.net", has performed the tests listed below against this email. Information: https://mxroutedocs.com/directadmin/spamfilters/ --- Content analysis details: (0.3 points) --- pts rule name description ---- ---------------------- ----------------------------------------- 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: githubusercontent.com] 0.0 RCVD_IN_DNSWL_BLOCKED RBL: ADMINISTRATOR NOTICE: The query to DNSWL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#DnsBlocklists-dnsbl-block for more information. [192.30.252.207 listed in list.dnswl.org] 0.0 RCVD_IN_MSPIKE_H3 RBL: Good reputation (+3) [192.30.252.207 listed in wl.mailspike.net] 1.5 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID_EF Message has a valid DKIM or DK signature from envelope-from domain -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.0 T_KAM_HTML_FONT_INVALID Test for Invalidly Named or Formatted Colors in HTML 0.0 RCVD_IN_MSPIKE_WL Mailspike good senders -1.0 MAILING_LIST_MULTI Multiple indicators imply a widely-seen list manager -0.0 DKIMWL_WL_HIGH DKIMwl.org - High trust sender SpamTally: Final spam score: 3 ----==_mimepart_6941993cb3f34_11911183338ed Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit sanjay7178 left a comment (kube-burner/kube-burner#1041) As per to @rsevilla87 suggestion having a hook config would be better . but as per @sferlin mentioned having synchronous child process to kube-burner parent process would be helpful like measuring etcd latency (p99 disk fsync duration ) , kubeapi server response time .... . my suggestion would ```yaml jobs: - name: rds-core jobIterations: 100 qps: 20 burst: 20 namespace: rds-core # ... other job settings ... hook: - cmd: ["/bin/bash", "-c", "pkill -SIGCONT crucible"] when: afterDeployment # We could accept other values like beforeChurn , beforeCleanup, beforeGC, afterGC, onEachIteration background: true ``` when crucible state becomes running then exactly kube-burner starts churning - Crucible is started externally before the test, initializes, and then Pauses itself (or is paused by a wrapper) waiting for a signal. - Kube-burner runs the workload and Kube-burner fires a Hook (shell command) right before the "Churn" phase begins. - In this case the hook sends a signal SIGCONT or touches a file (similar to `/share/start.lock`) to resume crucible. -- Reply to this email directly or view it on GitHub: https://github.com/kube-burner/kube-burner/issues/1041#issuecomment-3661674151 You are receiving this because you are subscribed to this thread. Message ID: ----==_mimepart_6941993cb3f34_11911183338ed Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
sanjay7178 left a comment (kube-burner/kube-burner#1041)

As per to @rsevilla87 suggestion h= aving a hook config would be better . but as per @sferlin mentioned having synchronous child process to kube-burner parent proces= s would be helpful like measuring etcd latency (p99 disk fsync duration )= , kubeapi server response time .... . my suggestion would

jobs:
  - name: rds-core
    jobIterations: 10=
0
    qps: 20
    burst: 20
    namespace: rds-cor=
e
    # ... other job sett=
ings ...

  hook:
  - cmd:  ["/bin/bash"=
, "-c", "pkill -SIGCONT crucible"]
    when: afterDeploym=
ent  # We could a=
ccept other values like beforeChurn , beforeCleanup, beforeGC, afterGC, o=
nEachIteration
    background: true<=
/span>

when crucible state becomes running then exactly kube-bur= ner starts churning

  • Crucible is started externally before the test, initializes, and then= Pauses itself (or is paused by a wrapper) waiting for a signal.
  • Kube-burner runs the workload and Kube-burner fires a Hook (shell com= mand) right before the "Churn" phase begins.
  • In this case the hook sends a signal SIGCONT or touches a file (simi= lar to /share/start.lock) to resume cr= ucible.

&m= dash;
Reply to this email directly, view it on Git= Hub, or unsubscribe.
You are receivin= g this because you are subscribed to this thread.3D""Message ID: <kube-burner/kube-burner/issues/1041/3661674151@github.com>

----==_mimepart_6941993cb3f34_11911183338ed-- From - Tue Dec 16 17:43:24 2025 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: Delivered-To: hi@josie.lol Received: from witcher.mxrouting.net by witcher.mxrouting.net with LMTP id WPN1JTGaQWnLszAAYBR5ng (envelope-from ) for ; Tue, 16 Dec 2025 17:43:13 +0000 Return-path: Envelope-to: github@josie.lol Delivery-date: Tue, 16 Dec 2025 17:43:13 +0000 Received: from out-21.smtp.github.com ([192.30.252.204]) by witcher.mxrouting.net with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.98) (envelope-from ) id 1vVZ4q-0000000E9jO-3GQL for github@josie.lol; Tue, 16 Dec 2025 17:43:13 +0000 Received: from github.com (hubbernetes-node-36c49b7.ac4-iad.github.net [10.52.131.21]) by smtp.github.com (Postfix) with ESMTPA id 5323A4010FC for ; Tue, 16 Dec 2025 09:43:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2023; t=1765906992; bh=EE2ebsHT8dEVJEH7mKGrqxgblVzhEmdYmwBtXTIWyRA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:List-Unsubscribe-Post: From; b=SBZw8P4Ol63etR94D/WDvlof8wC2XEGRlOVftraSRR2/lazxfPQlC4jKTlKp8yeWc RGHK9LKEuCWALaqCHmf5yCvmAvGFFZv8dhRorFvcGGvxWq2gqJP+HXsebL/dl4Bh4q VQG0wJf3Km6IygUpIImD9nf/Vcxi3tahi9mI9jRU= Date: Tue, 16 Dec 2025 09:43:12 -0800 From: purple Reply-To: Morganamilo/paru To: Morganamilo/paru Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [Morganamilo/paru] paru broken (Issue #1460) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_69419a304ff8f_be11183568c5"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: vvirtues X-GitHub-Recipient: pf