ankitsultana opened a new issue, #16674:
URL: https://github.com/apache/pinot/issues/16674

   The Quickstart code has gotten quite messy over time. In this instance, I 
wasn't able to run a server using a custom pinot-server.conf file. Also a lot 
of the logging is misleading. E.g. this log is likely not accurate if you 
override your ports, because the configOverrides kick in after this is logged.
   
   ```
   2025/08/23 04:08:24.489 INFO [StartServerCommand] [main] Executing command: 
StartServer -clusterName PinotCluster -serverHost null \
     -serverPort 8098 \
     -serverAdminPort 8097 \
     -serverGrpcPort 8090 \
     -serverMultistageServerPort 0 \
     -serverMultistageRunnerPort 0 \
     -dataDir /tmp/data/pinotServerData \
     -segmentDir /tmp/data/pinotSegments -zkAddress localhost:2191
   ```
   
   As part of this task it would be great if someone can:
   
   1. Test out manual cluster bring up using the "Manual Cluster" [instructions 
here](https://docs.pinot.apache.org/basics/getting-started/running-pinot-locally#setup-cluster-with-config-files).
 Specifically, you should try to bring up kafka, controller, broker and server 
using the commands in the Runbook, which work as expected. But if you try to 
bring up another server with a custom pinot-server.conf file, it might not work.
   2. Update the Runbook to let users know that they can use the 
pinot-server.conf files from resources as a sample config


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

To unsubscribe, e-mail: [email protected]

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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to