fjy commented on a change in pull request #7863: Added the web console to the 
quickstart tutorials and docs
URL: https://github.com/apache/incubator-druid/pull/7863#discussion_r294503246
 
 

 ##########
 File path: docs/content/tutorials/index.md
 ##########
 @@ -116,21 +117,13 @@ All persistent state such as the cluster metadata store 
and segments for the ser
 
 Later on, if you'd like to stop the services, CTRL-C to exit the 
`bin/start-micro-quickstart` script, which will terminate the Druid processes.
 
-### Resetting cluster state
-
-If you want a clean start after stopping the services, delete the `var` 
directory and run the `bin/start-micro-quickstart` script again.
-
-Once every service has started, you are now ready to load data.
+Once the cluster has started you can navigate to 
[http://localhost:8888](http://localhost:8888).
+This is the router node that also serves the Druid console.
 
-#### Resetting Kafka
+![Druid console](../tutorials/img/tutorial-quickstart-01.png "Druid console")
 
-If you completed [Tutorial: Loading stream data from 
Kafka](./tutorial-kafka.html) and wish to reset the cluster state, you should 
additionally clear out any Kafka state.
+It takes a few seconds for all the components to fully initialize and you 
might see some errors if you open the console immediately after starting the 
services.
 
 Review comment:
   It takes a few seconds for all the Druid processes to fully start up. If you 
open the console immediately after starting the services, you may see some 
errors that you can safely ignore.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

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

Reply via email to