Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Improving startup time with StartServiceManager command

See original GitHub issue

Currently, we are using the release apachepinot/pinot:0.5.0-SNAPSHOT-31d4194a2-2020073 with StartServiceManger command in our local dev setup in docker container mode.

Our observations are that it is CPUs having during startup and takes ~30-35 seconds to come up. Our initial observation is that it starts controller, server, and broker in order. Is there a way to parallelize this or places it can improve startup time?

Issue Analytics

State:
Created 3 years ago
Comments:8 (8 by maintainers)

Top GitHub Comments

1reaction

codefromthecryptcommented, Sep 28, 2020

PS I added debug around the time to call InetAddress.getLocalHost on our docker image. It had nothing to do with the near minute soup-to-nuts startup time

$ docker-compose logs pinot|egrep '(Resolved|since)'
pinot                   | 07:58:55,341 INFO  [main] command.StartServiceManagerCommand (StartServiceManagerCommand.java:285) - Starting a Pinot [SERVICE_MANAGER] at 0.016s since launch
pinot                   | Resolved localhost in 5ms
pinot                   | 07:59:15,678 INFO  [main] command.StartServiceManagerCommand (StartServiceManagerCommand.java:287) - Started Pinot [SERVICE_MANAGER] instance [ServiceManager_02f8740f86c8_7098] at 20.388s since launch
pinot                   | 07:59:15,734 INFO  [main] command.StartServiceManagerCommand (StartServiceManagerCommand.java:285) - Starting a Pinot [CONTROLLER] at 20.444s since launch
pinot                   | Resolved localhost in 0ms
pinot                   | Resolved localhost in 0ms
pinot                   | 07:59:31,450 INFO  [main] command.StartServiceManagerCommand (StartServiceManagerCommand.java:287) - Started Pinot [CONTROLLER] instance [Controller_02f8740f86c8_9000] at 36.161s since launch
pinot                   | 07:59:31,452 INFO  [Start a Pinot [BROKER]] command.StartServiceManagerCommand (StartServiceManagerCommand.java:285) - Starting a Pinot [BROKER] at 36.162s since launch
pinot                   | 07:59:31,452 INFO  [Start a Pinot [SERVER]] command.StartServiceManagerCommand (StartServiceManagerCommand.java:285) - Starting a Pinot [SERVER] at 36.163s since launch
pinot                   | Resolved localhost in 0ms
pinot                   | Resolved localhost in 0ms
pinot                   | Resolved localhost in 0ms
pinot                   | Resolved localhost in 0ms
pinot                   | 07:59:44,066 INFO  [Start a Pinot [SERVER]] command.StartServiceManagerCommand (StartServiceManagerCommand.java:287) - Started Pinot [SERVER] instance [Server_02f8740f86c8_8098] at 48.81s since launch
pinot                   | 07:59:44,345 INFO  [Start a Pinot [BROKER]] command.StartServiceManagerCommand (StartServiceManagerCommand.java:287) - Started Pinot [BROKER] instance [Broker_02f8740f86c8_8099] at 49.09s since launch
pinot                   | Resolved localhost in 0ms
pinot                   | Resolved localhost in 0ms
pinot                   | Resolved localhost in 0ms
pinot                   | Resolved localhost in 0ms
pinot                   | Resolved localhost in 0ms
pinot                   | *** Completed schema installation at 53s since launch

0reactions

codefromthecryptcommented, Sep 28, 2020

As a water mark when I over-allocate RAM to my docker engine (6GB to make sure it isn’t swapping) I get startup time like this when docker is already running schema registry, zookeeper and kafka…

pinot                   | 08:46:22,986 INFO  [main] command.StartServiceManagerCommand (StartServiceManagerCommand.java:285) - Starting a Pinot [SERVICE_MANAGER] at 0.007s since launch
pinot                   | 08:46:27,220 INFO  [main] command.StartServiceManagerCommand (StartServiceManagerCommand.java:287) - Started Pinot [SERVICE_MANAGER] instance [ServiceManager_20da8f16c3fb_7098] at 4.242s since launch
pinot                   | 08:46:27,246 INFO  [main] command.StartServiceManagerCommand (StartServiceManagerCommand.java:285) - Starting a Pinot [CONTROLLER] at 4.268s since launch
pinot                   | 08:46:32,430 INFO  [main] command.StartServiceManagerCommand (StartServiceManagerCommand.java:287) - Started Pinot [CONTROLLER] instance [Controller_20da8f16c3fb_9000] at 9.452s since launch
pinot                   | 08:46:32,432 INFO  [Start a Pinot [BROKER]] command.StartServiceManagerCommand (StartServiceManagerCommand.java:285) - Starting a Pinot [BROKER] at 9.453s since launch
pinot                   | 08:46:32,432 INFO  [Start a Pinot [SERVER]] command.StartServiceManagerCommand (StartServiceManagerCommand.java:285) - Starting a Pinot [SERVER] at 9.453s since launch
pinot                   | 08:46:35,755 INFO  [Start a Pinot [BROKER]] command.StartServiceManagerCommand (StartServiceManagerCommand.java:287) - Started Pinot [BROKER] instance [Broker_20da8f16c3fb_8099] at 12.777s since launch
pinot                   | 08:46:35,972 INFO  [Start a Pinot [SERVER]] command.StartServiceManagerCommand (StartServiceManagerCommand.java:287) - Started Pinot [SERVER] instance [Server_20da8f16c3fb_8098] at 12.993s since launch
pinot                   | *** Starting schema installation at 15s since container launch
pinot                   | *** Completed schema installation at 17s since container launch