Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

google-cloud-storage not working proper - missing settings gcsManagedLedgerOffloadBucket | gcsManagedLedgerOffloadRegion #299

Open
ton3r opened this issue Apr 4, 2024 · 1 comment

Comments

@ton3r
Copy link

ton3r commented Apr 4, 2024

Hi,

I've set up the cluster. During configuration I see that the offloading to GCP Buckets seems not to be working. I think it relates to missing properties.

I've followed the steps to use the k8s secret. But the json inside of the pod didn't contain any data. So I tried it with

helm upgrade pulsar datastax-pulsar/pulsar \
--set storageOffload.gcsServiceAccountJsonFile=bucket-pulsar-001-topic-offload.json \
--set storageOffload.gcsServiceAccountJsonFileContent=$(cat bucket-sa/bucket-pulsar-001-topic-offload.json | base64) \
--namespace pulsar \
--values values.yaml

Now the json contains the required content. But the UI shows me :

image

So I connect to a broker pod and do

I have no name!@pulsar-broker-677dbffbdc-jbkzw:/pulsar$ env | grep -i off
gcsManagedLedgerOffloadBucket=
managedLedgerOffloadDriver=google-cloud-storage
gcsManagedLedgerOffloadRegion=
gcsManagedLedgerOffloadServiceAccountKeyFile=/pulsar/gcp-service-account/bucket-pulsar-001-topic-offload.json

Values for gcsManagedLedgerOffloadBucket and gcsManagedLedgerOffloadRegion are not set. So I tried with

--set storageOffload.gcsManagedLedgerOffloadBucket=pulsar-001-topic-offload 
--set storageOffload.gcsManagedLedgerOffloadRegion=europe-west4 

but this is also not taken.

How to fix this?

@ton3r
Copy link
Author

ton3r commented Apr 5, 2024

After adding the values manual to config-map pulsar-broker the offloading takes place. A manual "Offload" on topic level offloades the things.

But the "False" from the screenshot in the "Namespace" Details is still there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant