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

KB485723: Platform Analytics Consumer failed to be up on Windows and "Failed to get offsets by times in 60001ms" appears in Platform-analytics-cosumer.err after upgrade to MicroStrategy Update 7


Community Admin

• Strategy


This article narrates Platform Analytics Consumer failed to be up and "Failed to get offsets by times in 60001ms" appears in Platform-analytics-cosumer.err after upgrade from MicroStrategy 2021 Update 5.2 to Update 7 due to a defect. A workaround is available in the current document. A solution/code fix for this issue is not available in current releases but is being reviewed for a future MicroStrategy release.

Symptom

After upgrade from Strategy 2021 Update 5.2 to Update 7, Platform Analytics Consumer failed to be up and "Failed to get offsets by times in 60001ms" appears in Platform-analytics-cosumer.err as shown below:
 

2022-10-07` 11:30:18,651 ERROR KafkaHealthCheck:87 - Failed to get offsets by times in 60001ms2022-10-07` 11:32:19,119 ERROR KafkaHealthCheck:87 - Failed to get offsets by times in 60001ms2022-10-07` 11:34:19,572 ERROR KafkaHealthCheck:87 - Failed to get offsets by times in 60001ms2022-10-07` 11:36:20,011 ERROR KafkaHealthCheck:87 - Failed to get offsets by times in 60000ms2022-10-07` 11:37:20,121 ERROR KafkaHealthCheck:87 - Failed to get offsets by times in 60000ms
 
- Please check the following: 

1. Check if Zookeeper servers on all nodes are up running: For Linux, run this command to get the PID if it is running: ps ax | grep java | grep -i QuorumPeerMain | grep -v grep | awk '{print $1}' For Windows, check if the "Apache Zookeeper" service is up running in Windows Services. 2. Check if Kafka servers on all nodes are up running: For Linux, run this command to get the PID if it is running: ps ax | grep -i 'kafka\.Kafka' | grep java | grep -v grep | awk '{print $1}' For Windows, check if the "Apache Kafka" service is up running in Windows Services. 3. Start Zookeeper and Kafka servers on all nodes: For Linux, run the following commands under <Strategy_INSTALL_DIRECTORY>/MessagingServices/Kafka/kafka*/bin directory: ./zookeeper-server-start.sh -daemon ../config/zookeeper.properties ./kafka-server-start.sh -daemon ../config/server.properties For Windows, start "Apache Zookeeper" and "Apache Kafka" services in Windows Services. Note: 1. If this is a clustered environment with multiple nodes of ZooKeeper server, you must start all nodes of ZooKeeper first.       2. Please start Platform Analytics Consumer once Zookeeper and Kafka servers are available. 

 
Health check failed at Kafka step but no specific error spotted in Kafka Server.log as shown below:
 
2022-10-07 11:37:20,140 INFO  KafkaHealthCheck:77 - Attempting to resolve Kafka host (127.0.0.1) to IP2022-10-07 11:37:20,140 INFO  KafkaHealthCheck:77 - Successfully resolved 127.0.0.1 to: [127.0.0.1]2022-10-07 11:37:20,141 INFO  KafkaHealthCheck:77 - Attempting to connect to Kafka at 127.0.0.1 on Port 9092 via Telnet2022-10-07 11:37:20,141 INFO  KafkaHealthCheck:77 - Successfully connected to above IP/Port via Telnet. Connectivity check healthy, please check your Kafka configuration settings.2022-10-07 11:37:20,142 INFO  KafkaHealthCheck:77 - Kafka cluster health check result is unhealthy.***********************************************************************************2022-10-07 11:37:20,142 INFO  PAConsumerHealthCheckList:68 - **************************  Health Check Summary  *********************************Platform Analytics Warehouse                               PASSPlatform Analytics Redis Server                             PASSPlatform Analytics Kafka Cluster                            FAIL

 
 

Cause

Currently this issue is being reviewed by Strategy for a potential code fix on an upcoming Strategy release.
 
 

Action

Strategy will continue to investigate and post updates as soon as they are available.
 
 

Workaround

  • Stop kafka and zookeeper (you might change the server startup type from automatic to manual
  • Go to folder of tmp\kafka-logs for example: C:\Program Files (x86)\MicroStrategy\Messaging Services\tmp\kafka-logs
  • Find ALL files named partition.metadata in the subfolder of kafka-logs: two examples showed below:
    • __consumer_offsets-0 
    • Mstr.PlatformAnalytics.ChangeJournal.AttributesAndForms-0
    • DELETE ALL partition.metadata files found above
    • Restart zookeeper and kafkaThen start PA consumer

 
Third Party Software Installation WARNING
The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.
 


Comment

0 comments

Details

Knowledge Article

Published:

October 19, 2022

Last Updated:

October 19, 2022