Pulsar Manager Backend keeps getting restarted on kubernetes deployment.

[unreal91]

Version 0.4.0 is deployed in Kubernetes, with external postgres configuration. Kindly let me know if there is any solution on this.

Logs for the pulsar manager pod.

6/1/2023, 11:58:41 PM
pulsar-pulsar-manager-7789cf998f-gk8zc
4a0130a91d2ab556944ea8913390b59b61f42330431779a5686de5ea19a538a3
2023-06-01 15:58:41,004 INFO spawned: 'pulsar-manager-backend' with pid 6504
6/1/2023, 11:58:41 PM
pulsar-pulsar-manager-7789cf998f-gk8zc
4a0130a91d2ab556944ea8913390b59b61f42330431779a5686de5ea19a538a3
2023-06-01 15:58:41,081 INFO exited: pulsar-manager-backend (exit status 1; not expected)
6/1/2023, 11:58:42 PM
pulsar-pulsar-manager-7789cf998f-gk8zc
4a0130a91d2ab556944ea8913390b59b61f42330431779a5686de5ea19a538a3
2023-06-01 15:58:42,085 INFO spawned: 'pulsar-manager-backend' with pid 6526
6/1/2023, 11:58:43 PM
pulsar-pulsar-manager-7789cf998f-gk8zc
4a0130a91d2ab556944ea8913390b59b61f42330431779a5686de5ea19a538a3
2023-06-01 15:58:43,153 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
6/1/2023, 11:58:43 PM
pulsar-pulsar-manager-7789cf998f-gk8zc
4a0130a91d2ab556944ea8913390b59b61f42330431779a5686de5ea19a538a3
2023-06-01 15:58:43,154 INFO exited: pulsar-manager-backend (exit status 1; not expected)
6/1/2023, 11:58:44 PM
pulsar-pulsar-manager-7789cf998f-gk8zc
4a0130a91d2ab556944ea8913390b59b61f42330431779a5686de5ea19a538a3
2023-06-01 15:58:44,157 INFO spawned: 'pulsar-manager-backend' with pid 6548
6/1/2023, 11:58:45 PM
pulsar-pulsar-manager-7789cf998f-gk8zc
4a0130a91d2ab556944ea8913390b59b61f42330431779a5686de5ea19a538a3
2023-06-01 15:58:45,227 INFO success: pulsar-manager-backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
6/1/2023, 11:58:45 PM
pulsar-pulsar-manager-7789cf998f-gk8zc
4a0130a91d2ab556944ea8913390b59b61f42330431779a5686de5ea19a538a3
2023-06-01 15:58:45,227 INFO exited: pulsar-manager-backend (exit status 1; not expected)

[packageman]

Refer to apache/pulsar-helm-chart#365, the reason is PULSAR_MANAGER_OPTS env in helm chart is not compatible with the v0.4.0 version。

[pocockn]

I'm seeing this as well. I tried removing the PULSAR_MANAGER_OPTS from the Helm chart but it still exits

[unreal91]

Finally workaround worked 0.4.0, this is causing due to application.properties changed to support herddb, thats why there are some variables like initialization mode etc., needs to override when you want to use external DB. Below configuration worked for me in config data:

SPRING_CONFIGURATION_FILE: "/pulsar-manager/pulsar-manager/application.properties"
REDIRECT_HOST: XXXXXXX
REDIRECT_PORT: "80"
SPRING_DATASOURCE_URL: XXXXXXXX
SPRING_DATASOURCE_DRIVERCLASSNAME: org.postgresql.Driver
URL: XXXXXXXXX
SPRING_DATASOURCE_USERNAME: XXXXXXX
SPRING_DATASOURCE_PASSWORD: XXXXXXX
SPRING_DATASOURCE_SCHEMA: classpath:/META-INF/sql/postgresql-schema.sql
SPRING_DATASOURCE_INITIALIZATIONMODE: never

You can always login to the pod and check the pulsar-manager.log file to see the error and override the spring environment variables accordingly