You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "AbleHou (via GitHub)" <gi...@apache.org> on 2024/03/11 15:25:01 UTC

[D] The registry already closed when starting broker after using the extensible load balancer [pulsar]

GitHub user AbleHou created a discussion: The registry already closed  when starting broker after using the extensible load balancer

broker configmap:
`apiVersion: v1
data:
  PF_connectorsDirectory: ./connectors
  PF_containerFactory: k8s
  PF_functionRuntimeFactoryClassName: org.apache.pulsar.functions.runtime.kubernetes.KubernetesRuntimeFactory
  PF_functionRuntimeFactoryConfigs_changeConfigMap: pulsar-functions-worker-config
  PF_functionRuntimeFactoryConfigs_changeConfigMapNamespace: pulsar
  PF_functionRuntimeFactoryConfigs_expectedMetricsCollectionInterval: "30"
  PF_functionRuntimeFactoryConfigs_installUserCodeDependencies: "true"
  PF_functionRuntimeFactoryConfigs_jobNamespace: pulsar
  PF_functionRuntimeFactoryConfigs_pulsarAdminUrl: http://pulsar-broker:8080/
  PF_functionRuntimeFactoryConfigs_pulsarDockerImageName: harbor.dev.wiqun.com:8443/ops/pulsar-all:3.2.0
  PF_functionRuntimeFactoryConfigs_pulsarRootDir: /pulsar
  PF_functionRuntimeFactoryConfigs_pulsarServiceUrl: pulsar://pulsar-broker:6650/
  PF_functionRuntimeFactoryConfigs_submittingInsidePod: "true"
  PF_kubernetesContainerFactory_changeConfigMap: pulsar-functions-worker-config
  PF_kubernetesContainerFactory_changeConfigMapNamespace: pulsar
  PF_kubernetesContainerFactory_expectedMetricsCollectionInterval: "30"
  PF_kubernetesContainerFactory_installUserCodeDependencies: "true"
  PF_kubernetesContainerFactory_jobNamespace: pulsar
  PF_kubernetesContainerFactory_pulsarAdminUrl: http://pulsar-broker:8080/
  PF_kubernetesContainerFactory_pulsarDockerImageName: harbor.dev.wiqun.com:8443/ops/pulsar-all:3.2.0
  PF_kubernetesContainerFactory_pulsarRootDir: /pulsar
  PF_kubernetesContainerFactory_pulsarServiceUrl: pulsar://pulsar-broker:6650/
  PF_kubernetesContainerFactory_submittingInsidePod: "true"
  PF_numFunctionPackageReplicas: "2"
  PF_pulsarFunctionsCluster: pulsar
  PULSAR_GC: |
    -XX:+UseG1GC -XX:MaxGCPauseMillis=10 -Dio.netty.leakDetectionLevel=disabled -Dio.netty.recycler.linkCapacity=1024 -XX:+ParallelRefProcEnabled -XX:+UnlockExperimentalVMOptions -XX:+DoEscapeAnalysis -XX:ParallelGCThreads=4 -XX:ConcGCThreads=4 -XX:G1NewSizePercent=50 -XX:+DisableExplicitGC -XX:-ResizePLAB -XX:+ExitOnOutOfMemoryError -XX:+PerfDisableSharedMem
  PULSAR_MEM: |
    -Xms128m -Xmx256m -XX:MaxDirectMemorySize=256m
  brokerServicePort: "6650"
  clusterName: pulsar
  configurationStoreServers: pulsar-zookeeper:2181
  exposeTopicLevelMetricsInPrometheus: "true"
  functionsWorkerEnabled: "true"
  loadBalancerLoadSheddingStrategy: org.apache.pulsar.broker.loadbalance.extensions.scheduler.TransferShedder
  loadManagerClassName: org.apache.pulsar.broker.loadbalance.extensions.ExtensibleLoadManagerImpl
  managedLedgerDefaultAckQuorum: "2"
  managedLedgerDefaultEnsembleSize: "2"
  managedLedgerDefaultWriteQuorum: "2"
  metadataStoreOperationTimeoutSeconds: "300"
  metadataStoreSessionTimeoutMillis: "30000"
  numHttpServerThreads: "8"
  statusFilePath: /pulsar/status
  transactionCoordinatorEnabled: "true"
  webServicePort: "8080"
  zookeeperServers: pulsar-zookeeper:2181
kind: ConfigMap`

GitHub link: https://github.com/apache/pulsar/discussions/22244

----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org


Re: [D] The registry already closed when starting broker after using the extensible load balancer [pulsar]

Posted by "AbleHou (via GitHub)" <gi...@apache.org>.
GitHub user AbleHou edited a discussion: The registry already closed  when starting broker after using the extensible load balancer

broker configmap:
apiVersion: v1
data:
  PF_connectorsDirectory: ./connectors
  PF_containerFactory: k8s
  PF_functionRuntimeFactoryClassName: org.apache.pulsar.functions.runtime.kubernetes.KubernetesRuntimeFactory
  PF_functionRuntimeFactoryConfigs_changeConfigMap: pulsar-functions-worker-config
  PF_functionRuntimeFactoryConfigs_changeConfigMapNamespace: pulsar
  PF_functionRuntimeFactoryConfigs_expectedMetricsCollectionInterval: "30"
  PF_functionRuntimeFactoryConfigs_installUserCodeDependencies: "true"
  PF_functionRuntimeFactoryConfigs_jobNamespace: pulsar
  PF_functionRuntimeFactoryConfigs_pulsarAdminUrl: http://pulsar-broker:8080/
  PF_functionRuntimeFactoryConfigs_pulsarDockerImageName: harbor.dev.wiqun.com:8443/ops/pulsar-all:3.2.0
  PF_functionRuntimeFactoryConfigs_pulsarRootDir: /pulsar
  PF_functionRuntimeFactoryConfigs_pulsarServiceUrl: pulsar://pulsar-broker:6650/
  PF_functionRuntimeFactoryConfigs_submittingInsidePod: "true"
  PF_kubernetesContainerFactory_changeConfigMap: pulsar-functions-worker-config
  PF_kubernetesContainerFactory_changeConfigMapNamespace: pulsar
  PF_kubernetesContainerFactory_expectedMetricsCollectionInterval: "30"
  PF_kubernetesContainerFactory_installUserCodeDependencies: "true"
  PF_kubernetesContainerFactory_jobNamespace: pulsar
  PF_kubernetesContainerFactory_pulsarAdminUrl: http://pulsar-broker:8080/
  PF_kubernetesContainerFactory_pulsarDockerImageName: harbor.dev.wiqun.com:8443/ops/pulsar-all:3.2.0
  PF_kubernetesContainerFactory_pulsarRootDir: /pulsar
  PF_kubernetesContainerFactory_pulsarServiceUrl: pulsar://pulsar-broker:6650/
  PF_kubernetesContainerFactory_submittingInsidePod: "true"
  PF_numFunctionPackageReplicas: "2"
  PF_pulsarFunctionsCluster: pulsar
  PULSAR_GC: |
    -XX:+UseG1GC -XX:MaxGCPauseMillis=10 -Dio.netty.leakDetectionLevel=disabled -Dio.netty.recycler.linkCapacity=1024 -XX:+ParallelRefProcEnabled -XX:+UnlockExperimentalVMOptions -XX:+DoEscapeAnalysis -XX:ParallelGCThreads=4 -XX:ConcGCThreads=4 -XX:G1NewSizePercent=50 -XX:+DisableExplicitGC -XX:-ResizePLAB -XX:+ExitOnOutOfMemoryError -XX:+PerfDisableSharedMem
  PULSAR_MEM: |
    -Xms128m -Xmx256m -XX:MaxDirectMemorySize=256m
  brokerServicePort: "6650"
  clusterName: pulsar
  configurationStoreServers: pulsar-zookeeper:2181
  exposeTopicLevelMetricsInPrometheus: "true"
  functionsWorkerEnabled: "true"
  loadBalancerLoadSheddingStrategy: org.apache.pulsar.broker.loadbalance.extensions.scheduler.TransferShedder
  loadManagerClassName: org.apache.pulsar.broker.loadbalance.extensions.ExtensibleLoadManagerImpl
  managedLedgerDefaultAckQuorum: "2"
  managedLedgerDefaultEnsembleSize: "2"
  managedLedgerDefaultWriteQuorum: "2"
  metadataStoreOperationTimeoutSeconds: "300"
  metadataStoreSessionTimeoutMillis: "30000"
  numHttpServerThreads: "8"
  statusFilePath: /pulsar/status
  transactionCoordinatorEnabled: "true"
  webServicePort: "8080"
  zookeeperServers: pulsar-zookeeper:2181
kind: ConfigMap

GitHub link: https://github.com/apache/pulsar/discussions/22244

----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org


Re: [D] The registry already closed when starting broker after using the extensible load balancer [pulsar]

Posted by "AbleHou (via GitHub)" <gi...@apache.org>.
GitHub user AbleHou added a comment to the discussion: The registry already closed  when starting broker after using the extensible load balancer

I use image apachepulsar/pulsar-all:3.2.0.
broker error log:
2024-03-11T15:51:03,908+0000 [main] ERROR org.apache.pulsar.broker.PulsarService - Failed to start Pulsar service: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: The registry already closed.
org.apache.pulsar.broker.PulsarServerException: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: The registry already closed.
        at org.apache.pulsar.broker.namespace.NamespaceService.registerNamespace(NamespaceService.java:409) ~[org.apache.pulsar-pulsar-broker-3.2.0.jar:3.2.0]
        at org.apache.pulsar.broker.namespace.NamespaceService.registerBootstrapNamespaces(NamespaceService.java:343) ~[org.apache.pulsar-pulsar-broker-3.2.0.jar:3.2.0]
        at org.apache.pulsar.broker.PulsarService.start(PulsarService.java:874) ~[org.apache.pulsar-pulsar-broker-3.2.0.jar:3.2.0]
        at org.apache.pulsar.PulsarBrokerStarter$BrokerStarter.start(PulsarBrokerStarter.java:276) ~[org.apache.pulsar-pulsar-broker-3.2.0.jar:3.2.0]
        at org.apache.pulsar.PulsarBrokerStarter.main(PulsarBrokerStarter.java:356) ~[org.apache.pulsar-pulsar-broker-3.2.0.jar:3.2.0]
Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: The registry already closed.
        at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:396) ~[?:?]
        at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2073) ~[?:?]
        at org.apache.pulsar.broker.namespace.NamespaceService.registerNamespace(NamespaceService.java:380) ~[org.apache.pulsar-pulsar-broker-3.2.0.jar:3.2.0]
        ... 4 more
Caused by: java.lang.IllegalStateException: The registry already closed.
        at org.apache.pulsar.broker.loadbalance.extensions.BrokerRegistryImpl.checkState(BrokerRegistryImpl.java:241) ~[org.apache.pulsar-pulsar-broker-3.2.0.jar:3.2.0]
        at org.apache.pulsar.broker.loadbalance.extensions.BrokerRegistryImpl.lookupAsync(BrokerRegistryImpl.java:159) ~[org.apache.pulsar-pulsar-broker-3.2.0.jar:3.2.0]
        at org.apache.pulsar.broker.loadbalance.extensions.ExtensibleLoadManagerImpl.lambda$getBrokerLookupData$13(ExtensibleLoadManagerImpl.java:524) ~[org.apache.pulsar-pulsar-broker-3.2.0.jar:3.2.0]
        at java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1187) ~[?:?]
        at java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2309) ~[?:?]
        at org.apache.pulsar.broker.loadbalance.extensions.ExtensibleLoadManagerImpl.getBrokerLookupData(ExtensibleLoadManagerImpl.java:524) ~[org.apache.pulsar-pulsar-broker-3.2.0.jar:3.2.0]
        at org.apache.pulsar.broker.loadbalance.extensions.ExtensibleLoadManagerImpl.lambda$assign$8(ExtensibleLoadManagerImpl.java:473) ~[org.apache.pulsar-pulsar-broker-3.2.0.jar:3.2.0]
        at org.apache.pulsar.broker.loadbalance.extensions.ExtensibleLoadManagerImpl.lambda$dedupeLookupRequest$15(ExtensibleLoadManagerImpl.java:563) ~[org.apache.pulsar-pulsar-broker-3.2.0.jar:3.2.0]
        at java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1708) ~[?:?]
        at org.apache.pulsar.broker.loadbalance.extensions.ExtensibleLoadManagerImpl.dedupeLookupRequest(ExtensibleLoadManagerImpl.java:562) ~[org.apache.pulsar-pulsar-broker-3.2.0.jar:3.2.0]
        at org.apache.pulsar.broker.loadbalance.extensions.ExtensibleLoadManagerImpl.assign(ExtensibleLoadManagerImpl.java:460) ~[org.apache.pulsar-pulsar-broker-3.2.0.jar:3.2.0]
        at org.apache.pulsar.broker.loadbalance.extensions.ExtensibleLoadManagerImpl.tryAcquiringOwnership(ExtensibleLoadManagerImpl.java:546) ~[org.apache.pulsar-pulsar-broker-3.2.0.jar:3.2.0]
        at org.apache.pulsar.broker.namespace.NamespaceService.registerNamespace(NamespaceService.java:380) ~[org.apache.pulsar-pulsar-broker-3.2.0.jar:3.2.0]
        ... 4 more

GitHub link: https://github.com/apache/pulsar/discussions/22244#discussioncomment-8752946

----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org


Re: [D] The registry already closed when starting broker after using the extensible load balancer [pulsar]

Posted by "AbleHou (via GitHub)" <gi...@apache.org>.
GitHub user AbleHou added a comment to the discussion: The registry already closed  when starting broker after using the extensible load balancer

It ' s okay after upgrade 3.2.1

GitHub link: https://github.com/apache/pulsar/discussions/22244#discussioncomment-8754117

----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org


Re: [D] The registry already closed when starting broker after using the extensible load balancer [pulsar]

Posted by "lhotari (via GitHub)" <gi...@apache.org>.
GitHub user lhotari added a comment to the discussion: The registry already closed  when starting broker after using the extensible load balancer

@AbleHou What is the logged exception? do you have a similar problem with Pulsar 3.2.1 ?

GitHub link: https://github.com/apache/pulsar/discussions/22244#discussioncomment-8748058

----
This is an automatically sent email for commits@pulsar.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@pulsar.apache.org