EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB484058: Apache Zookeeper prints EndofStreamException warning entries in its log file


Sigit Pambudi

Software Architect • MicroStrategy


This article explains why Apache Zookeeper prints the following EndofStreamException warning entry it its log file: Unable to Read Additional Data from Client.

Description 


Strategy Telemetry is an integral part of Strategy Intelligence Enterprise that provides Messaging Services for Intelligence Server logs and a central backbone for Platform Analytics. To provide these functionalities, Telemetry depends on a third-party Apache Zookeeper service. To ensure the performance and availability of many important services, especially Apache Zookeeper, Strategy provides a seamless way for system administrators to monitor and control these services through the Topology view in MicroStrategy Workstation.
The following screenshot illustrates how Topology can be used to monitor Strategy services installed on multiple nodes. 

ka02R000000g6RqQAI_0EM2R000000nwMO.jpeg

Various Strategy and third-party services are monitored by Topology by sending health check signals on a periodic basis. For monitoring Apache Zookeeper service, Topology sends TCP connection requests to the service port, which has a default port number of 2181, at every pre-determined interval (the default interval is 10 seconds). These TCP checks are kept lightweight and short-lived to minimize the performance impact to Zookeeper as its target service. The short-lived TCP heatlh checks, however, are detected by Zookeeper as a connection request from a client that got disconnected and furter needs to be closed explicitly. Whenever this clean-up action is performed, Zookeeper will print the following warning entries into its log file. 

ka02R000000g6RqQAI_0EM2R000000nwV1.jpeg

The warning entries are expected during Zookeeper's normal operations and can be safely ignored. 
By default, the log file is in the following paths:
 
In Windows

C:\Program Files (x86)\MicroStrategy\Messaging Services\Kafka\kafka_2.11-1.1.0\logs\zookeeper\server.log

In Linux
/opt/MicroStrategy/MessagingServices/Kafka/kafka_2.11-1.1.0/logs/zookeeper.out

 


Comment

0 comments

Details

Knowledge Article

Published:

February 21, 2020

Last Updated:

February 21, 2020