https://datahubproject.io logo
Join Slack
Powered by
Following the guide- Deploying to AWS | DataHub (<...
# troubleshoot
g
Following the guide- Deploying to AWS | DataHub (datahubproject.io) Tried multiple times but my prerequisites-cp-schema-registry keeps failing.
Copy code
AbhisekRoy:ghostrider abhisekroy$ kubectl describe pod prerequisites-cp-schema-registry-7cc6786995-dn2zs
Name:             prerequisites-cp-schema-registry-7cc6786995-dn2zs
Namespace:        default
Priority:         0
Service Account:  default
Node:             ip-172-1-1-176.ec2.internal/172.1.1.176
Start Time:       Sat, 18 Feb 2023 21:05:45 +0530
Labels:           app=cp-schema-registry
                  pod-template-hash=7cc6786995
                  release=prerequisites
Annotations:      <http://kubernetes.io/psp|kubernetes.io/psp>: eks.privileged
                  <http://prometheus.io/port|prometheus.io/port>: 5556
                  <http://prometheus.io/scrape|prometheus.io/scrape>: true
Status:           Running
IP:               172.1.1.65
IPs:
  IP:           172.1.1.65
Controlled By:  ReplicaSet/prerequisites-cp-schema-registry-7cc6786995
Containers:
  prometheus-jmx-exporter:
    Container ID:  <containerd://a29bd4a7217422f8a2f5007054e5d7f1f0194da8275142cf51a09754133345d>2
    Image:         solsson/kafka-prometheus-jmx-exporter@sha256:6f82e2b0464f50da8104acd7363fb9b995001ddff77d248379f8788e78946143
    Image ID:      <http://docker.io/solsson/kafka-prometheus-jmx-exporter@sha256:6f82e2b0464f50da8104acd7363fb9b995001ddff77d248379f8788e78946143|docker.io/solsson/kafka-prometheus-jmx-exporter@sha256:6f82e2b0464f50da8104acd7363fb9b995001ddff77d248379f8788e78946143>
    Port:          5556/TCP
    Host Port:     0/TCP
    Command:
      java
      -XX:+UnlockExperimentalVMOptions
      -XX:+UseCGroupMemoryLimitForHeap
      -XX:MaxRAMFraction=1
      -XshowSettings:vm
      -jar
      jmx_prometheus_httpserver.jar
      5556
      /etc/jmx-schema-registry/jmx-schema-registry-prometheus.yml
    State:          Running
      Started:      Sat, 18 Feb 2023 21:05:49 +0530
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /etc/jmx-schema-registry from jmx-config (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-p54q9 (ro)
  cp-schema-registry-server:
    Container ID:   <containerd://8af9eb7e78ebb4245d34593a328e9fe4b1ebfc358162eaec6a595547a4aa2c2>8
    Image:          confluentinc/cp-schema-registry:6.0.1
    Image ID:       <http://docker.io/confluentinc/cp-schema-registry@sha256:b52e16cf232e3c9acd677ae8944de813e16fa541a367d9f805b300c5d2be1a1f|docker.io/confluentinc/cp-schema-registry@sha256:b52e16cf232e3c9acd677ae8944de813e16fa541a367d9f805b300c5d2be1a1f>
    Ports:          8081/TCP, 5555/TCP
    Host Ports:     0/TCP, 0/TCP
    State:          Running
      Started:      Sat, 18 Feb 2023 21:16:13 +0530
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Sat, 18 Feb 2023 21:12:42 +0530
      Finished:     Sat, 18 Feb 2023 21:13:27 +0530
    Ready:          True
    Restart Count:  6
    Environment:
      SCHEMA_REGISTRY_HOST_NAME:                      (v1:status.podIP)
      SCHEMA_REGISTRY_LISTENERS:                     <http://0.0.0.0:8081>
      SCHEMA_REGISTRY_KAFKASTORE_BOOTSTRAP_SERVERS:  prerequisites-kafka:9092
      SCHEMA_REGISTRY_KAFKASTORE_GROUP_ID:           prerequisites
      SCHEMA_REGISTRY_MASTER_ELIGIBILITY:            true
      SCHEMA_REGISTRY_HEAP_OPTS:                     -Xms512M -Xmx512M
      JMX_PORT:                                      5555
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-p54q9 (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             True 
  ContainersReady   True 
  PodScheduled      True 
Volumes:
  jmx-config:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      prerequisites-cp-schema-registry-jmx-configmap
    Optional:  false
  kube-api-access-p54q9:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 <http://node.kubernetes.io/not-ready:NoExecute|node.kubernetes.io/not-ready:NoExecute> op=Exists for 300s
                             <http://node.kubernetes.io/unreachable:NoExecute|node.kubernetes.io/unreachable:NoExecute> op=Exists for 300s
Events:
  Type     Reason     Age                    From               Message
  ----     ------     ----                   ----               -------
  Normal   Scheduled  10m                    default-scheduler  Successfully assigned default/prerequisites-cp-schema-registry-7cc6786995-dn2zs to ip-172-1-1-176.ec2.internal
  Normal   Pulling    10m                    kubelet            Pulling image "solsson/kafka-prometheus-jmx-exporter@sha256:6f82e2b0464f50da8104acd7363fb9b995001ddff77d248379f8788e78946143"
  Normal   Pulled     10m                    kubelet            Successfully pulled image "solsson/kafka-prometheus-jmx-exporter@sha256:6f82e2b0464f50da8104acd7363fb9b995001ddff77d248379f8788e78946143" in 3.016715265s
  Normal   Created    10m                    kubelet            Created container prometheus-jmx-exporter
  Normal   Started    10m                    kubelet            Started container prometheus-jmx-exporter
  Normal   Pulling    10m                    kubelet            Pulling image "confluentinc/cp-schema-registry:6.0.1"
  Normal   Pulled     10m                    kubelet            Successfully pulled image "confluentinc/cp-schema-registry:6.0.1" in 19.845033941s
  Normal   Created    7m17s (x4 over 10m)    kubelet            Created container cp-schema-registry-server
  Normal   Started    7m17s (x4 over 10m)    kubelet            Started container cp-schema-registry-server
  Normal   Pulled     5m42s (x4 over 9m25s)  kubelet            Container image "confluentinc/cp-schema-registry:6.0.1" already present on machine
  Warning  BackOff    32s (x25 over 8m40s)   kubelet            Back-off restarting failed container
AbhisekRoy:ghostrider abhisekroy$
This is what I get on running describe pod
I have 4 nodes in my cluster
Would really be grateful if someone has a clue.
o
What do the logs for schema registry say? Looks like there was a similar issue in this thread here
g
Copy code
AbhisekRoy:DataHub-Deployment abhisekroy$ kubectl logs prerequisites-cp-schema-registry-7cc6786995-b9xc4 -c cp-schema-registry-server
===> User
uid=1000(appuser) gid=1000(appuser) groups=1000(appuser)
===> Configuring ...
===> Running preflight checks ... 
===> Check if Kafka is healthy ...
[main] INFO org.apache.kafka.clients.admin.AdminClientConfig - AdminClientConfig values: 
        bootstrap.servers = [prerequisites-kafka:9092]
        client.dns.lookup = use_all_dns_ips
        client.id = 
        <http://connections.max.idle.ms|connections.max.idle.ms> = 300000
        <http://default.api.timeout.ms|default.api.timeout.ms> = 60000
        <http://metadata.max.age.ms|metadata.max.age.ms> = 300000
        metric.reporters = []
        metrics.num.samples = 2
        metrics.recording.level = INFO
        <http://metrics.sample.window.ms|metrics.sample.window.ms> = 30000
        receive.buffer.bytes = 65536
        <http://reconnect.backoff.max.ms|reconnect.backoff.max.ms> = 1000
        <http://reconnect.backoff.ms|reconnect.backoff.ms> = 50
        <http://request.timeout.ms|request.timeout.ms> = 30000
        retries = 2147483647
        <http://retry.backoff.ms|retry.backoff.ms> = 100
        sasl.client.callback.handler.class = null
        sasl.jaas.config = null
        sasl.kerberos.kinit.cmd = /usr/bin/kinit
        sasl.kerberos.min.time.before.relogin = 60000
        sasl.kerberos.service.name = null
        sasl.kerberos.ticket.renew.jitter = 0.05
        sasl.kerberos.ticket.renew.window.factor = 0.8
        sasl.login.callback.handler.class = null
        sasl.login.class = null
        sasl.login.refresh.buffer.seconds = 300
        sasl.login.refresh.min.period.seconds = 60
        sasl.login.refresh.window.factor = 0.8
        sasl.login.refresh.window.jitter = 0.05
        sasl.mechanism = GSSAPI
        security.protocol = PLAINTEXT
        security.providers = null
        send.buffer.bytes = 131072
        ssl.cipher.suites = null
        ssl.enabled.protocols = [TLSv1.2, TLSv1.3]
        ssl.endpoint.identification.algorithm = https
        ssl.engine.factory.class = null
        ssl.key.password = null
        ssl.keymanager.algorithm = SunX509
        ssl.keystore.location = null
        ssl.keystore.password = null
        ssl.keystore.type = JKS
        ssl.protocol = TLSv1.3
        ssl.provider = null
        ssl.secure.random.implementation = null
        ssl.trustmanager.algorithm = PKIX
        ssl.truststore.location = null
        ssl.truststore.password = null
        ssl.truststore.type = JKS

[main] INFO org.apache.kafka.common.utils.AppInfoParser - Kafka version: 6.0.1-ccs
[main] INFO org.apache.kafka.common.utils.AppInfoParser - Kafka commitId: 9c1fbb3db1e0d69d
[main] INFO org.apache.kafka.common.utils.AppInfoParser - Kafka startTimeMs: 1676958179902
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[kafka-admin-client-thread | adminclient-1] INFO org.apache.kafka.clients.admin.internals.AdminMetadataManager - [AdminClient clientId=adminclient-1] Metadata update failed
org.apache.kafka.common.errors.TimeoutException: Call(callName=fetchMetadata, deadlineMs=1676958209912, tries=1, nextAllowedTryMs=1676958210013) timed out at 1676958209913 after 1 attempt(s)
Caused by: org.apache.kafka.common.errors.TimeoutException: Timed out waiting to send the call.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[main] ERROR io.confluent.admin.utils.ClusterStatus - Error while getting broker list.
java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.TimeoutException: Call(callName=listNodes, deadlineMs=1676958219910, tries=1, nextAllowedTryMs=1676958220011) timed out at 1676958219911 after 1 attempt(s)
        at org.apache.kafka.common.internals.KafkaFutureImpl.wrapAndThrow(KafkaFutureImpl.java:45)
        at org.apache.kafka.common.internals.KafkaFutureImpl.access$000(KafkaFutureImpl.java:32)
        at org.apache.kafka.common.internals.KafkaFutureImpl$SingleWaiter.await(KafkaFutureImpl.java:89)
        at org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:260)
        at io.confluent.admin.utils.ClusterStatus.isKafkaReady(ClusterStatus.java:149)
        at io.confluent.admin.utils.cli.KafkaReadyCommand.main(KafkaReadyCommand.java:150)
Caused by: org.apache.kafka.common.errors.TimeoutException: Call(callName=listNodes, deadlineMs=1676958219910, tries=1, nextAllowedTryMs=1676958220011) timed out at 1676958219911 after 1 attempt(s)
Caused by: org.apache.kafka.common.errors.TimeoutException: Timed out waiting for a node assignment.
[kafka-admin-client-thread | adminclient-1] WARN org.apache.kafka.clients.NetworkClient - [AdminClient clientId=adminclient-1] Connection to node -1 (prerequisites-kafka/10.100.205.147:9092) could not be established. Broker may not be available.
[main] INFO io.confluent.admin.utils.ClusterStatus - Expected 1 brokers but found only 0. Trying to query Kafka for metadata again ...
[main] ERROR io.confluent.admin.utils.ClusterStatus - Expected 1 brokers but found only 0. Brokers found [].
@orange-night-91387 This is what the logs are showing
Copy code
AbhisekRoy:DataHub-Deployment abhisekroy$ kubectl describe pod prerequisites-kafka-0 
Name:             prerequisites-kafka-0
Namespace:        default
Priority:         0
Service Account:  prerequisites-kafka
Node:             <none>
Labels:           <http://app.kubernetes.io/component=kafka|app.kubernetes.io/component=kafka>
                  <http://app.kubernetes.io/instance=prerequisites|app.kubernetes.io/instance=prerequisites>
                  <http://app.kubernetes.io/managed-by=Helm|app.kubernetes.io/managed-by=Helm>
AbhisekRoy:DataHub-Deployment abhisekroy$ kubectl describe pod prerequisites-kafka-0 
Name:             prerequisites-kafka-0
Namespace:        default
Priority:         0
Service Account:  prerequisites-kafka
Node:             <none>
Labels:           <http://app.kubernetes.io/component=kafka|app.kubernetes.io/component=kafka>
                  <http://app.kubernetes.io/instance=prerequisites|app.kubernetes.io/instance=prerequisites>
                  <http://app.kubernetes.io/managed-by=Helm|app.kubernetes.io/managed-by=Helm>
                  <http://app.kubernetes.io/name=kafka|app.kubernetes.io/name=kafka>
                  controller-revision-hash=prerequisites-kafka-6cfb98d49f
                  <http://helm.sh/chart=kafka-17.1.0|helm.sh/chart=kafka-17.1.0>
                  <http://statefulset.kubernetes.io/pod-name=prerequisites-kafka-0|statefulset.kubernetes.io/pod-name=prerequisites-kafka-0>
Annotations:      <http://kubernetes.io/psp|kubernetes.io/psp>: eks.privileged
Status:           Pending
IP:               
IPs:              <none>
Controlled By:    StatefulSet/prerequisites-kafka
Containers:
  kafka:
    Image:       <http://docker.io/bitnami/kafka:3.2.0-debian-10-r4|docker.io/bitnami/kafka:3.2.0-debian-10-r4>
    Ports:       9092/TCP, 9093/TCP
    Host Ports:  0/TCP, 0/TCP
    Command:
      /scripts/setup.sh
    Liveness:   tcp-socket :kafka-client delay=10s timeout=5s period=10s #success=1 #failure=3
    Readiness:  tcp-socket :kafka-client delay=5s timeout=5s period=10s #success=1 #failure=6
    Environment:
      BITNAMI_DEBUG:                                       false
      MY_POD_IP:                                            (v1:status.podIP)
      MY_POD_NAME:                                         prerequisites-kafka-0 (v1:metadata.name)
      KAFKA_CFG_ZOOKEEPER_CONNECT:                         prerequisites-zookeeper
      KAFKA_INTER_BROKER_LISTENER_NAME:                    INTERNAL
      KAFKA_CFG_LISTENER_SECURITY_PROTOCOL_MAP:            INTERNAL:PLAINTEXT,CLIENT:PLAINTEXT
      KAFKA_CFG_LISTENERS:                                 INTERNAL://:9093,CLIENT://:9092
      KAFKA_CFG_ADVERTISED_LISTENERS:                      INTERNAL://$(MY_POD_NAME).prerequisites-kafka-headless.default.svc.cluster.local:9093,CLIENT://$(MY_POD_NAME).prerequisites-kafka-headless.default.svc.cluster.local:9092
      ALLOW_PLAINTEXT_LISTENER:                            yes
      KAFKA_ZOOKEEPER_PROTOCOL:                            PLAINTEXT
      KAFKA_VOLUME_DIR:                                    /bitnami/kafka
      KAFKA_LOG_DIR:                                       /opt/bitnami/kafka/logs
      KAFKA_CFG_DELETE_TOPIC_ENABLE:                       false
      KAFKA_CFG_AUTO_CREATE_TOPICS_ENABLE:                 true
      KAFKA_HEAP_OPTS:                                     -Xmx1024m -Xms1024m
      KAFKA_CFG_LOG_FLUSH_INTERVAL_MESSAGES:               10000
      KAFKA_CFG_LOG_FLUSH_INTERVAL_MS:                     1000
      KAFKA_CFG_LOG_RETENTION_BYTES:                       1073741824
      KAFKA_CFG_LOG_RETENTION_CHECK_INTERVALS_MS:          300000
      KAFKA_CFG_LOG_RETENTION_HOURS:                       168
      KAFKA_CFG_MESSAGE_MAX_BYTES:                         1000012
      KAFKA_CFG_LOG_SEGMENT_BYTES:                         1073741824
      KAFKA_CFG_LOG_DIRS:                                  /bitnami/kafka/data
      KAFKA_CFG_DEFAULT_REPLICATION_FACTOR:                1
      KAFKA_CFG_OFFSETS_TOPIC_REPLICATION_FACTOR:          1
      KAFKA_CFG_TRANSACTION_STATE_LOG_REPLICATION_FACTOR:  1
      KAFKA_CFG_TRANSACTION_STATE_LOG_MIN_ISR:             1
      KAFKA_CFG_NUM_IO_THREADS:                            8
      KAFKA_CFG_NUM_NETWORK_THREADS:                       3
      KAFKA_CFG_NUM_PARTITIONS:                            1
      KAFKA_CFG_NUM_RECOVERY_THREADS_PER_DATA_DIR:         1
      KAFKA_CFG_SOCKET_RECEIVE_BUFFER_BYTES:               102400
      KAFKA_CFG_SOCKET_REQUEST_MAX_BYTES:                  104857600
      KAFKA_CFG_SOCKET_SEND_BUFFER_BYTES:                  102400
      KAFKA_CFG_ZOOKEEPER_CONNECTION_TIMEOUT_MS:           6000
      KAFKA_CFG_AUTHORIZER_CLASS_NAME:                     
      KAFKA_CFG_ALLOW_EVERYONE_IF_NO_ACL_FOUND:            true
      KAFKA_CFG_SUPER_USERS:                               User:admin
    Mounts:
      /bitnami/kafka from data (rw)
      /opt/bitnami/kafka/logs from logs (rw)
      /scripts/setup.sh from scripts (rw,path="setup.sh")
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-g9hrv (ro)
Volumes:
  data:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  data-prerequisites-kafka-0
    ReadOnly:   false
  scripts:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      prerequisites-kafka-scripts
    Optional:  false
  logs:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:     
    SizeLimit:  <unset>
  kube-api-access-g9hrv:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 <http://node.kubernetes.io/not-ready:NoExecute|node.kubernetes.io/not-ready:NoExecute> op=Exists for 300s
                             <http://node.kubernetes.io/unreachable:NoExecute|node.kubernetes.io/unreachable:NoExecute> op=Exists for 300s
Events:                      <none>
This is how the kafka pod looks
Any clue @bulky-electrician-72362?
b
you kafka pod is not comming up. it might be because of not sufficient resources or the PVC is not ready
since events are <none> it's hard to tell what's happening
try 
kubectl get pvc
and see wether they are ready?
g
@bulky-electrician-72362 this is the result
Would you be able to join a Google meet for 5min @bulky-electrician-72362?
We can resolve it quickly then.
b
not familiar with AWS EKS, but what does it show if you run 
kubectl get storageClass
o
Also try describing the pvc, since it is in pending state it should give you a message about why it is in pending state.
h
@orange-night-91387 - I am facing the same issue. Could you direct me on what steps were taken on resolving the above ?
7 Views
Open in Slack
PreviousNext
Powered by