docs: added pecularities of v5 local setup

Author: maxceem

README.md

@@ -86,28 +86,32 @@ Microservice to manage CRUD operations for all things Projects.
   The project service will be served on `http://localhost:8001`.
 
 ### Import sample metadata & projects
+
 ```bash
 CONNECT_USER_TOKEN=<connect user token> npm run demo-data
 ```
-This command will create sample metadata entries in the DB (duplicate what is currently in development environment).
+To retrieve data from DEV env we have to provide a valid user token (`CONNECT_USER_TOKEN`). You may login to http://connect.topcoder-dev.com and find the Bearer token in the request headers using browser dev tools.
 
-To retrieve data from DEV env we need to provide a valid user token. You may login to http://connect.topcoder-dev.com and find the Bearer token in the request headers using browser dev tools.
+This command for importing data uses API to create demo data. Which has a few pecularities:
+- data in DB would be for sure created
+- data in ElasticSearch Index (ES) would be only created if services [project-processor-es](https://github.com/topcoder-platform/project-processor-es) and [tc-bus-api](https://github.com/topcoder-platform/tc-bus-api) are also started locally. If you don't start them, then imported data wouldn't be indexed in ES, and would be only added to DB. You may start them locally separately, or better use `local/full/docker-compose.yml` as described [next section](#local-deployment-with-other-topcoder-services) which would start them automatically.
+   - **NOTE** During data importing a lot of records has to be indexed in ES, so you have to wait about 5-10 minutes after `npm run demo-data` is finished until imported data is indexed in ES. You may watch logs of `project-processor-es` to see if its done or no.
 
 ### Local Deployment with other Topcoder Services.
 
 * There exists an alternate `docker-compose.yml` file that can be used to spawn containers for the following services:
 
-|  Service | Name | Port  |
-|----------|:-----:|:----:|
-| PostGreSQL DB | db | 5432  |
-| ElasticSearch | esearch | 9200,9300 |
-| RabbitMQ | queue | 5672, 15672  |
-| Zookeeper | zookeeper | 2181  |
-| Kafka | kafka | 9092  |
-| [tc-bus-api](https://github.com/topcoder-platform/tc-bus-api) | tc-bus-api | 8002  |
-| [project-processor-es](https://github.com/topcoder-platform/project-processor-es) | project-processor-es | 5000  |
-| [tc-notifications-api](https://github.com/topcoder-platform/tc-notifications) | tc-notifications-api | 4000  |
-| [tc-notifications-processor](https://github.com/topcoder-platform/tc-notifications) | tc-notifications-processor | 4001  |
+  |  Service | Name | Port  |
+  |----------|:-----:|:----:|
+  | PostGreSQL DB | db | 5432  |
+  | ElasticSearch | esearch | 9200,9300 |
+  | RabbitMQ | queue | 5672, 15672  |
+  | Zookeeper | zookeeper | 2181  |
+  | Kafka | kafka | 9092  |
+  | [tc-bus-api](https://github.com/topcoder-platform/tc-bus-api) | tc-bus-api | 8002  |
+  | [project-processor-es](https://github.com/topcoder-platform/project-processor-es) | project-processor-es | 5000  |
+  | [tc-notifications-api](https://github.com/topcoder-platform/tc-notifications) | tc-notifications-api | 4000  |
+  | [tc-notifications-processor](https://github.com/topcoder-platform/tc-notifications) | tc-notifications-processor | 4001  |
 
 * To have kafka create a list of desired topics on startup, there exists a file with the path `local/full/kafka-client/topics.txt`. Each line from the file will be added as a topic.
 * To run these services simply run the following commands:
@@ -134,6 +138,15 @@ To retrieve data from DEV env we need to provide a valid user token. You may log
 
 * The containers have been configured such that all Topcoder services will wait until all the topics listed in `local/full/kafka-client/topics.txt` have been created. To monitor the progress of topic creation, you can view the logs of the `kafka-client` service, which will exit when all topics have been created.
 
+* **WARNING**<br>
+  After all the containers are started, make sure that `project-processor-es` service started successfully, as sometimes it doesn't start successfully as Kafka wasn't yet properly started at that moment. So run `docker-compose logs -f project-processor-es` to see its logs, you should see 3 lines with text `Subscribed to project.action.` like:
+  ```
+  project-processor-es_1        | 2019-12-18T11:10:12.849Z DEBUG no-kafka-client Subscribed to project.action.update:0 offset 0 leader 96e65c46c746:9092
+  project-processor-es_1        | 2019-12-18T11:10:12.851Z DEBUG no-kafka-client Subscribed to project.action.delete:0 offset 0 leader 96e65c46c746:9092
+  project-processor-es_1        | 2019-12-18T11:10:12.852Z DEBUG no-kafka-client Subscribed to project.action.create:0 offset 0 leader 96e65c46c746:9092
+  ```
+  If you don't see such lines, restart `project-processor-es` service ONLY by running `docker-compose restart project-processor-es`.
+
 ### Run Connect App with Project Service locally
 
 To be able to run [Connect App](https://github.com/appirio-tech/connect-app) with the local setup of Project Service we have to do two things: