Pull-through cache reports redice cache MISSes
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 24
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 39
Description
The following instructions are to be executed in the oci-env container.
- Install Java 11
dnf install -y java-11-openjdk-devel
- Install maven from source
cd /opt sudo wget https://downloads.apache.org/maven/maven-3/3.9.6/binaries/apache-maven-3.9.6-bin.tar.gz
sudo tar -xvzf apache-maven-3.9.6-bin.tar.gz sudo mv apache-maven-3.9.6 /opt/maven
vi /etc/profile.d/maven.sh
export M2_HOME=/opt/maven
export MAVEN_HOME=/opt/maven
export PATH=${M2_HOME}/bin:${PATH}
chmod +x /etc/profile.d/maven.sh
source /etc/profile.d/maven.sh
- Confirm Maven is installed and using Java 11
mvn -v
Apache Maven 3.9.6
Java version: 11.0.xx, vendor: Red Hat
Java home: /usr/lib/jvm/java-11-openjdk-…
- Setup a pull-through cache repository in Pulp
Follow all the instructions here: https://pulpproject.org/pulp_maven/docs/user/guides/create-cache/
- Modify
/etc/init/pulpcore-contentto include cache HIT/MISS in the access log
--access-logformat '%a %t "%r" %s %b "%{Referer}i" "%{User-Agent}i" cache:"%{X-PULP-CACHE}o" artifact_size:"%{X-PULP-ARTIFACT-SIZE}o" rh_org_id:"%{X-RH-ORG-ID}o"' \
-
Build galley from the root of the project
mvn install -DskipTests
- Clean up the maven cache
rm -rf ~/.m2/repository/
- Build galley again
mvn install -DskipTests
- Notice in the access log that some .jar files have a cache MISS
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.
Research direction
Reproduce the steps in the oci-env container, including the pull-through cache setup and the Galley build. Start with the /etc/init/pulpcore-content access-log configuration and inspect the cache HIT/MISS entries for .jar files during the second build. Done means the unexpected MISS behavior is explained and the issue has a clearly verified outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100