You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using a GitHub clone prior to yesterday's database initialization scripts. However, I do have organizations and licenses added through the services and today (using the chapter 11 code) I successfully queried an organization (after getting authenticated). I did a clean build before bringing up the containers. With the volume of logged messages, the authentication and organizations calls were slow (about 2 seconds), but they worked.
Kibana and the logged messages repeatedly show, 1 partitions have leader brokers without a matching listener The logged output is streaming these messages for both consumer-2 and producer-2 and orgChangeTopic-0. I ran an organization query using the organization service. It was slow, but it worked, as did the prior authentication. Kibana doesn't show the traceId.
From Kibana:
logger_name:org.apache.kafka.clients.NetworkClient message:[Consumer clientId=consumer-2, groupId=licensingGroup] 1 partitions have leader brokers without a matching listener, including [orgChangeTopic-0] application_name:licensing-service thread_name:KafkaConsumerDestination{consumerDestinationName='orgChangeTopic', partitions=1, dlqName='null'}.container-0-C-1 tags:manningPublications @Version:1 host:licensing-service.docker_backend @timestamp:Sep 16, 2020 @ 21:20:43.535 level:WARN level_value:30,000 port:36,810 _id:jIndmXQBTrxKlPkYL4kf _type:_doc _index:logstash-2020.09.17-000001 _score: -
Please see attachment for two attempts. I did not see any memory errors. However, in one attempt the configuration service did not start. I checked my system to confirm port 8071 wasn't already in use and it wasn't. The second attempt (search for +++++ to get to the start of the listing), seems to show the organization service unable to connect to logstash on port 5000.
I'm using a GitHub clone prior to yesterday's database initialization scripts. However, I do have organizations and licenses added through the services and today (using the chapter 11 code) I successfully queried an organization (after getting authenticated). I did a clean build before bringing up the containers. With the volume of logged messages, the authentication and organizations calls were slow (about 2 seconds), but they worked.
Kibana and the logged messages repeatedly show,
1 partitions have leader brokers without a matching listener
The logged output is streaming these messages for both consumer-2 and producer-2 and orgChangeTopic-0. I ran an organization query using the organization service. It was slow, but it worked, as did the prior authentication. Kibana doesn't show the traceId.From Kibana:
Please see attachment for two attempts. I did not see any memory errors. However, in one attempt the configuration service did not start. I checked my system to confirm port 8071 wasn't already in use and it wasn't. The second attempt (search for +++++ to get to the start of the listing), seems to show the organization service unable to connect to logstash on port 5000.
Chapter 11 Container Start Issues.txt
The text was updated successfully, but these errors were encountered: