Troubleshooting Typesense Issues in Kubectl v1.26
TLDR Arnob and Rubai face issues with Typesense erasing data. Jason and Kishore Nallan suggest HA setup and persistent volume usage. Sai recommends the Typesense Kubernetes operator but Arnob experiences new errors.
1
Jul 30, 2023 (4 months ago)
Arnob
08:26 AMJul 31, 2023 (4 months ago)
Rubai
01:35 PMJason
04:08 PMJason
04:09 PMRubai
07:53 PMJason
08:31 PMAug 01, 2023 (4 months ago)
Rubai
07:14 AMRubai
09:09 AMKishore Nallan
09:12 AMRubai
09:12 AMRubai
09:13 AMKishore Nallan
09:13 AMKishore Nallan
09:14 AMArnob
10:32 AMKishore Nallan
10:33 AMArnob
12:15 PMKishore Nallan
12:19 PMcc Sai who maintains it can help if you run into any issues.
Sai
12:22 PMretain
policy else the data will be lost. Happy to help if you need anything.Arnob
12:28 PM1
Aug 02, 2023 (4 months ago)
Arnob
09:13 AMThe above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/kopf/_cogs/aiokits/aiotasks.py", line 108, in guard
await coro
File "/usr/local/lib/python3.9/site-packages/kopf/_core/engines/peering.py", line 176, in keepalive
await touch(
File "/usr/local/lib/python3.9/site-packages/kopf/_core/engines/peering.py", line 221, in touch
rsp = await patching.patch_obj(
File "/usr/local/lib/python3.9/site-packages/kopf/_cogs/clients/patching.py", line 47, in patch_obj
patched_body = await api.patch(
File "/usr/local/lib/python3.9/site-packages/kopf/_cogs/clients/api.py", line 155, in patch
response = await request(
File "/usr/local/lib/python3.9/site-packages/kopf/_cogs/clients/auth.py", line 45, in wrapper
return await fn(*args, **kwargs, context=context)
File "/usr/local/lib/python3.9/site-packages/kopf/_cogs/clients/api.py", line 85, in request
await errors.check_response(response) # but do not parse it!
File "/usr/local/lib/python3.9/site-packages/kopf/_cogs/clients/errors.py", line 150, in check_response
raise cls(payload, status=response.status) from e
kopf._cogs.clients.errors.APIForbiddenError: (' "default" is forbidden: User "system:serviceaccount:typesense-rnd-v4:typesense-operator-sa" cannot patch resource "clusterkopfpeerings" in API group "" at the cluster scope', {'kind': 'Status', 'apiVersion': 'v1', 'metadata': {}, 'status': 'Failure', 'message': ' "default" is forbidden: User "system:serviceaccount:typesense-rnd-v4:typesense-operator-sa" cannot patch resource "clusterkopfpeerings" in API group "" at the cluster scope', 'reason': 'Forbidden', 'details': {'name': 'default', 'group': '', 'kind': 'clusterkopfpeerings'}, 'code': 403})
Arnob
09:20 AMoperator-config.yaml
it delete deployment.apps/typesense-operator
also cant port-forward get typesense service.Sai
09:21 AMArnob
09:22 AMTypesense
Indexed 3005 threads (79% resolved)
Similar Threads
Issues deploying Typesense to AWS EKS
Pavan had issues when deploying Typesense to AWS EKS. Kishore Nallan suggested deployment to plain EC2 instances and provided the API key information. Eventually, Pavan resolved the issue with Helm.
Issues with Typesense and k8s Snapshot Restoration
Arnob experienced data loss and errors with Typesense in k8s. Kishore Nallan explained corruption could be from premature pod termination. To resolve, Kishore Nallan suggested deleting the data directory on the malfunctioning pod for automatic restoration from the leader.
Typesense Issues in Kubernetes Environment
siva.sunkara experienced Typesense issues in Kubernetes and shared logs. Kishore Nallan recommended stand-alone nodes and shared a Github issue thread. Sergio suggested fine-tuning Kubernetes deployment and linked to a working setup.
Typesense Error in Unit Testing for Python
Mehdi was encountering errors while running unit tests for Typesense functionalities in Python. Through discussion with Kishore Nallan, they recognized resource constraints might be causing the issue during JSONL file import. As suggested by Kishore Nallan, adding a short sleep after the import resolved the problem.
"Resolving Startup Issue with Typesense Single Replica Set in Local `K8s` Setup"
Vishal encountered issues starting a Typesense single replica set due to directory permission issues. Kishore Nallan suggested checking if the volume was accessible for writes. Vishal resolved the problem by adjusting permissions on the host.