You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2026/07/22 08:27:00 UTC
[jira] [Commented] (KNOX-3388) Single-EKU test gateway startup is slow/flaky: batch credential-store alias creation
[ https://issues.apache.org/jira/browse/KNOX-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18098090#comment-18098090 ]
ASF subversion and git services commented on KNOX-3388:
-------------------------------------------------------
Commit 9f4b8e7fbe9c4c09f79d27c58448c704fca8288d in knox's branch refs/heads/master from Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=9f4b8e7fb ]
KNOX-3388: Improve alias creation during EKU mode testing (#1316)
> Single-EKU test gateway startup is slow/flaky: batch credential-store alias creation
> ------------------------------------------------------------------------------------
>
> Key: KNOX-3388
> URL: https://issues.apache.org/jira/browse/KNOX-3388
> Project: Apache Knox
> Issue Type: Improvement
> Affects Versions: 3.0.0
> Reporter: Sandor Molnar
> Assignee: Sandor Molnar
> Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The single-EKU compose entrypoint (gateway-single-eku.sh) creates its 5 credential-store aliases with one {{knoxcli.sh create-alias}} call each. Every call is a cold JVM boot (~6-8s), so ~30-40s elapses before the gateway JVM even starts. In CI the "sleep 30" wait starts at container start and is fully consumed by alias creation, so the gateway binds 8443 only after {{pytest}} connects -> intermittent "Connection refused" in the single-EKU mTLS suite.
> Fix: create all 5 aliases in a single {{knoxcli.sh create-aliases}} invocation.
> Container-start -> "Started gateway on port 8443" drops from ~35s to ~9s.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)