g0715158 opened a new issue #8245:
URL: https://github.com/apache/pulsar/issues/8245


   Describe the bug
   The ip I configured is not this. The current error occasionally occurs when 
the number of cluster producers is large.
   
   logs:
   2020-10-10 09:50:47.120 [pulsar-external-listener-137-1] WARN  
org.apache.pulsar.client.impl.PulsarClientImpl - [topic: 
persistent://tenant-test-1/namespace-test-1/topic-t
   est-37] Could not get connection while getPartitionedTopicMetadata -- Will 
try again in 100 ms  
   2020-10-10 09:50:47.120 [pulsar-external-listener-180-1] WARN  
org.apache.pulsar.client.impl.PulsarClientImpl - [topic: 
persistent://tenant-test-1/namespace-test-1/topic-t
   est-49] Could not get connection while getPartitionedTopicMetadata -- Will 
try again in 100 ms  
   2020-10-10 09:50:47.121 [pulsar-client-io-43-32] WARN  
org.apache.pulsar.client.impl.ConnectionPool - Failed to open connection to 
pulsar:6650 : java.net.UnknownHostExcept
   ion: failed to resolve 'pulsar' after 4 queries   
   2020-10-10 09:50:47.123 [pulsar-client-io-30-1] WARN  
org.apache.pulsar.client.impl.ConnectionPool - Failed to open connection to 
pulsar:6650 : java.net.UnknownHostExcepti
   on: failed to resolve 'pulsar' after 4 queries   
   
   
   To Reproduce
   Steps to reproduce the behavior:
   
   Additional context:
   version:2.5.2
   class:NamespaceStatsAggregator
   method:getTopicStats


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to