Distributed caching updates
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- distributed-systems, documentation
Research direction
Start by locating the “Distributed caching with JCache” and “Distributed session caching” topics, then review the follow-on SEC380 work in #5704. Get the provider examples and troubleshooting information from @jvanhill; done means provider configuration guidance and a JCache troubleshooting topic are added, with the session-caching topic’s disposition decided.
Written by the indexing model from the issue text.
Description
As a follow-on to SEC380 work in #5704, we need to create some new topics that show how to config JCache for different providers.
- create new topics under the Distributed caching with JCache topic.
Distributed caching with JCache
Configure Infinispan
Configure Datagrid (on OpenShift)
Configure Hazelcast
Configure eXtreme Scale
or possibly a single topic JCache provider configuration, with subheadings for examples and anchor links at top of topic.
- add a JCache troubleshooting topic
@jvanhill to provide examples/info.
- Also consider moving/ removing the Distributed session caching topic.
- Dominant language
- No language data
- Stars
- 14
- Forks
- 58
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 21
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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/docs
-
source mismatchOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenLiberty/docs#8579 ·
Maintainers usually reply within 1 day
-
Jandex extended pathOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
OpenLiberty/docs#8451 · 1 comment ·
Maintainers usually reply within 1 day
-
CVE update for 26.0.0.10Possibly taken @ramkumar-k-9286 claimed this 19 days ago. Open26.0.0.10 Developer reviewed
OpenLiberty/docs#8563 · 5 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
26.0.0.11
Difficulty 5/5 Over a week Newbie friendliness 25/100
OpenLiberty/docs#8548 ·
Maintainers usually reply within 1 day
-
26.0.0.12
Difficulty 4/5 3-5 days Newbie friendliness 45/100
OpenLiberty/docs#8529 · 1 comment ·
Maintainers usually reply within 1 day
All issues in OpenLiberty/docs
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug needs-triage provider v2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openeverest/openeverest#3400 ·
Maintainers usually reply within 1 day
-
[Bug] SP communication warmup hardcodes device="cuda", breaking every non-CUDA acceleratorPossibly taken @li-lizhe claimed this today. Openinstallation platform scope: attention scope: distributed scope: inference
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hao-ai-lab/FastVideo#1987 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarperFast/harper-pro#1076 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
rivet-dev/rivet#5891 · 1 comment ·
Maintainers usually reply within 1 day