OpenLiberty / OpenLiberty/ci.docker

restore checkpoint app image start slower when using sessionCache with infinispan

Open
#552 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

InstantOn
Dominant language
Shell
Stars
48
Forks
60
Avg merge
3h 2m
Merged PRs (30d)
3

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
kubernetes
Domain
infrastructure, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.