[FOLIO-2246] test/update config for Okapi Created: 09/Sep/19  Updated: 03/Jun/20  Resolved: 05/Nov/19

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: Ian Hardy Assignee: Ian Hardy
Resolution: Done Votes: 0
Labels: devops, platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to OKAPI-733 Document why getLock fails Closed
relates to OKAPI-759 Prevent Vertx thread blocked warning Closed
Sprint: CP: sprint 74, CP: sprint 76, CP: sprint 73, CP: sprint 75, CP: sprint 72
Story Points: 3
Development Team: Core: Platform

 Description   

Ran into problems with blocked threads when posting to the install endpoint with loadSample and loadReference set to true. The current hazelcast config in is very minimal:

https://github.com/folio-org/folio-ansible/blob/master/roles/okapi-kubernetes/templates/hazelcast-configmap.yml.j2

Review documentation and update hazelcast config as needed: https://vertx.io/docs/vertx-hazelcast/java/



 Comments   
Comment by Ian Hardy [ 11/Sep/19 ]

First thing to try:
Update to latest released okapi (2.32.0) and re-run playbook that caused errors. Currently running 2.32.0-SNAPSHOT.

Comment by Ian Hardy [ 17/Sep/19 ]

Updated to 2.32.0 and scaled up to 3 nodes, need to test creating a new tenant, using install endpoint w/loadSample and loadReference

Comment by Ian Hardy [ 04/Nov/19 ]

Clustering trouble might be due to how arguments/variables are declared int he kubernetes yaml for okapi. The args refer to variables defined in the same file. Theoretically, this is fine, but the order of those variables isn't preserved on updates via either rancher or kubectl (or both).

Comment by Ian Hardy [ 04/Nov/19 ]

We're using hazelcast.xml and rbac rules that are scoped to a namespace, but applying the rules to the default service account (which is shared accross namespaces). Each namespace should have a service account for the okapi cluster in that namespace.

Generated at Thu Feb 08 23:19:16 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.