mdnoorshid opened a new issue, #15628:
URL: https://github.com/apache/druid/issues/15628
Hi team,
We have migrated our druid cluster from vm based deployment to kubernetes.
Every components are up but historical is not able to load the segments and
showing status as **Could not get load queue info**.
Coordinator is able to connect with zookeeper.
**Here is the logs of coordinator:**
`ervisor - [pharos-web-telemetry] supervisor is running.
2024-01-05T06:45:54,574 DEBUG [SegmentAllocQueue-0]
org.apache.druid.indexing.common.actions.SegmentAllocationQueue - Processed [0]
batches, next execution in [500 ms]
2024-01-05T06:45:55,074 DEBUG [SegmentAllocQueue-0]
org.apache.druid.indexing.common.actions.SegmentAllocationQueue - Processed [0]
batches, next execution in [500 ms]
2024-01-05T06:45:55,574 DEBUG [SegmentAllocQueue-0]
org.apache.druid.indexing.common.actions.SegmentAllocationQueue - Processed [0]
batches, next execution in [500 ms]
2024-01-05T06:45:56,074 DEBUG [SegmentAllocQueue-0]
org.apache.druid.indexing.common.actions.SegmentAllocationQueue - Processed [0]
batches, next execution in [500 ms]
2024-01-05T06:45:56,574 DEBUG [SegmentAllocQueue-0]
org.apache.druid.indexing.common.actions.SegmentAllocationQueue - Processed [0]
batches, next execution in [500 ms]
2024-01-05T06:45:57,074 DEBUG [SegmentAllocQueue-0]
org.apache.druid.indexing.common.actions.SegmentAllocationQueue - Processed [0]
batches, next execution in [500 ms]
2024-01-05T06:45:57,575 DEBUG [SegmentAllocQueue-0]
org.apache.druid.indexing.common.actions.SegmentAllocationQueue - Processed [0]
batches, next execution in [500 ms]
2024-01-05T06:45:58,075 DEBUG [SegmentAllocQueue-0]
org.apache.druid.indexing.common.actions.SegmentAllocationQueue - Processed [0]
batches, next execution in [500 ms]
2024-01-05T06:45:58,575 DEBUG [SegmentAllocQueue-0]
org.apache.druid.indexing.common.actions.SegmentAllocationQueue - Processed [0]
batches, next execution in [500 ms]
2024-01-05T06:45:59,075 DEBUG [SegmentAllocQueue-0]
org.apache.druid.indexing.common.actions.SegmentAllocationQueue - Processed [0]
batches, next execution in [500 ms]
2024-01-05T06:45:59,575 DEBUG [SegmentAllocQueue-0]
org.apache.druid.indexing.common.actions.SegmentAllocationQueue - Processed [0]
batches, next execution in [500 ms]
2024-01-05T06:46:00,075 DEBUG [SegmentAllocQueue-0]
org.apache.druid.indexing.common.actions.SegmentAllocationQueue - Processed [0]
batches, next execution in [500 ms]`
Here is the logs of Historical
`2024-01-05T06:36:40,444 INFO [main]
org.apache.druid.java.util.common.lifecycle.Lifecycle - Starting lifecycle
[module] stage [SERVER]
2024-01-05T06:36:40,447 INFO [main] org.eclipse.jetty.server.Server -
jetty-9.4.53.v20231009; built: 2023-10-09T12:29:09.265Z; git:
27bde00a0b95a1d5bbee0eae7984f891d2d0f8c9; jvm 17.0.9+9-Debian-1deb12u1
2024-01-05T06:36:40,544 INFO [main] org.eclipse.jetty.server.session -
DefaultSessionIdManager workerName=node0
2024-01-05T06:36:40,544 INFO [main] org.eclipse.jetty.server.session - No
SessionScavenger set, using defaults
2024-01-05T06:36:40,545 INFO [main] org.eclipse.jetty.server.session - node0
Scavenging every 600000ms
2024-01-05T06:36:40,739 INFO [main]
com.sun.jersey.server.impl.application.WebApplicationImpl - Initiating Jersey
application, version 'Jersey: 1.19.4 05/24/2017 03:20 PM'
2024-01-05T06:36:41,850 INFO [main]
org.eclipse.jetty.server.handler.ContextHandler - Started
o.e.j.s.ServletContextHandler@4fc2933e{/,null,AVAILABLE}
2024-01-05T06:36:41,859 INFO [main]
org.eclipse.jetty.server.AbstractConnector - Started
ServerConnector@726a5e6a{HTTP/1.1, (http/1.1)}{0.0.0.0:8083}
2024-01-05T06:36:41,921 INFO [main]
org.eclipse.jetty.util.ssl.SslContextFactory -
x509=X509@3c4e23be(druid-service.dev.carbon.gcp.lowes.com,h=[druid-service.dev.carbon.gcp.lowes.com],a=[],w=[])
for
IdentityCheckOverrideSslContextFactory@1d6a0962[provider=null,keyStore=file:///opt/druid/ssl/pharos-keystore.jks,trustStore=null]
2024-01-05T06:36:41,932 INFO [main]
org.eclipse.jetty.server.AbstractConnector - Started
ServerConnector@7ec8db0c{SSL, (ssl, http/1.1)}{0.0.0.0:8283}
2024-01-05T06:36:41,932 INFO [main] org.eclipse.jetty.server.Server -
Started @15799ms
2024-01-05T06:36:41,951 INFO [main]
org.apache.druid.java.util.common.lifecycle.Lifecycle - Starting lifecycle
[module] stage [ANNOUNCEMENTS]
2024-01-05T06:36:42,046 INFO [main]
org.apache.druid.curator.discovery.CuratorDruidNodeAnnouncer - Announced self
[{"druidNode":{"service":"druid/historical","host":"240.38.32.231","bindOnHost":false,"plaintextPort":8083,"port":-1,"tlsPort":8283,"enablePlaintextPort":true,"enableTlsPort":true},"nodeType":"historical","services":{"dataNodeService":{"type":"dataNodeService","tier":"hot","maxSize":24000000000,"type":"historical","serverType":"historical","priority":0},"lookupNodeService":{"type":"lookupNodeService","lookupTier":"__default"}},"startTime":"2024-01-05T06:36:38.736Z"}].
2024-01-05T06:36:42,046 INFO [main]
org.apache.druid.java.util.common.lifecycle.Lifecycle - Successfully started
lifecycle [module]
`
Could some one help on this resolution and if not at least let me know how
to debug this issue.
I am using **druid 28.0.0 version**
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
