restore checkpoint app image start slower when using sessionCache with infinispan
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- kubernetes
- Domain
- infrastructure, performance
Research direction
Start with the server.xml configuration in the issue and compare the pod startup logs in pods-logs.zip with runs that omit httpSessionCache. Review the linked Slack discussions for existing investigation, then define done as identifying the source of the added startup delay and documenting or implementing a verified reduction.
Written by the indexing model from the issue text.
Description
Restore eBuy checkpoint app image on OCP. The app is configured to have httpSessionCache with infinispan with the following in server.xml
<server>
<featureManager>
<feature>appSecurity-4.0</feature>
<feature>sessionCache-1.0</feature>
</featureManager>
<library id="DatagridLib">
<fileset dir="${server.config.dir}/datagrid" includes="*.jar"/>
</library>
<cacheManager id="CacheManager" uri="file:///${server.config.dir}/datagrid/infinispan_hotrod.props">
<properties infinispan.client.hotrod.uri="hotrod://${INFINISPAN_USER}:${INFINISPAN_PASS}@${INFINISPAN_HOST}:${INFINISPAN_PORT}"/>
<cachingProvider providerClass="org.infinispan.jcache.remote.JCachingProvider" jCacheLibraryRef="DatagridLib" />
</cacheManager>
<httpSessionCache cacheManagerRef="CacheManager" cacheSeparator="_"/>
</server>
When restore eBuy app on OCP without using httpSessionCache, it takes less than 1 second or sometimes just a little over 1 second for the server to start, but when using httpSessionCache, it takes about 12 seconds for the first app pod to start and about 4 to 5 seconds for the later pods
I see that there are many org.infinispan.HOTROD messages in the logs that add more time to the server start time
pods' logs: pods-logs.zip
Slack discussion: https://ibm-cloud.slack.com/archives/C03MR7EC3NG/p1718041901887979?thread_ts=1717187652.885869&cid=C03MR7EC3NG and https://ibm-cloud.slack.com/archives/C03MR7EC3NG/p1718226721233629
- Dominant language
- Shell
- Stars
- 48
- Forks
- 60
- Avg merge
- 3h 2m
- Merged PRs (30d)
- 3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenLiberty/ci.docker
-
zenhub-dev
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenLiberty/ci.docker#747 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
OpenLiberty/ci.docker#649 · 10 comments ·
-
zenhub-dev
OpenLiberty/ci.docker#642 · 1 comment · 1 assignee ·
-
zenhub-dev
OpenLiberty/ci.docker#568 · 1 comment · 1 assignee ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
OpenLiberty/ci.docker#567 · 9 comments ·
All issues in OpenLiberty/ci.docker
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
chore
Difficulty 1/5 Under an hour Newbie friendliness 91/100
alunduil/alunduil-chezmoi#792 ·