2020-01-27 15:59:34 -08:00
|
|
|
# Frequently Asked Questions (FAQ)
|
|
|
|
|
|
|
|
|
|
1. How can I check if [MXE](what/mxe.md) Kafka topics are created?
|
|
|
|
|
|
|
|
|
|
You can use a utility like [kafkacat](https://github.com/edenhill/kafkacat) to list all topics.
|
|
|
|
|
You can run below command to see the Kafka topics created in your Kafka broker.
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
kafkacat -L -b localhost:9092
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
Confirm that `MetadataChangeEvent` & `MetadataAuditEvent` topics exist besides the default ones. Example response as below:
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
Metadata for all topics (from broker 1: localhost:9092/1):
|
|
|
|
|
1 brokers:
|
|
|
|
|
broker 1 at localhost:9092
|
|
|
|
|
5 topics:
|
|
|
|
|
topic "_schemas" with 1 partitions:
|
|
|
|
|
partition 0, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
topic "__consumer_offsets" with 50 partitions:
|
|
|
|
|
partition 0, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 1, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 2, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 3, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 4, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 5, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 6, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 7, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 8, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 9, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 10, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 11, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 12, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 13, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 14, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 15, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 16, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 17, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 18, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 19, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 20, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 21, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 22, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 23, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 24, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 25, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 26, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 27, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 28, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 29, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 30, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 31, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 32, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 33, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 34, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 35, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 36, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 37, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 38, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 39, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 40, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 41, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 42, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 43, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 44, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 45, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 46, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 47, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 48, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
partition 49, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
topic "MetadataChangeEvent" with 1 partitions:
|
|
|
|
|
partition 0, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
topic "__confluent.support.metrics" with 1 partitions:
|
|
|
|
|
partition 0, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
topic "MetadataAuditEvent" with 1 partitions:
|
|
|
|
|
partition 0, leader 1, replicas: 1, isrs: 1
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
2. How can I check if search indices are created in Elasticsearch?
|
|
|
|
|
|
|
|
|
|
You can run below command to see the search indices created in your Elasticsearch.
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
curl http://localhost:9200/_cat/indices
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
Confirm that `datasetdocument` & `corpuserinfodocument` indices exist besides the default ones. Example response as below:
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
yellow open .monitoring-es-6-2020.01.27 hNu-jjU3Tl2SKKFdXzjxHQ 1 1 27279 34 14.8mb 14.8mb
|
|
|
|
|
yellow open .watcher-history-6-2020.01.27 70BeSxOkQiCsBCGNtZNfAw 1 1 1210 0 1mb 1mb
|
|
|
|
|
yellow open corpuserinfodocument VCupUjstS4SrZHLDruwVzg 5 1 2 0 11kb 11kb
|
|
|
|
|
yellow open .monitoring-kibana-6-2020.01.27 pfJy8HOxRQKG-RQKexMKkA 1 1 1456 0 688.3kb 688.3kb
|
|
|
|
|
yellow open .watches jmJxYOjrSamqlTi-UIrxTA 1 1 4 0 19.6kb 19.6kb
|
|
|
|
|
yellow open datasetdocument 5HB_IpjYSbOh3QUSUeuwgA 5 1 3 0 27.9kb 27.9kb
|
|
|
|
|
yellow open .monitoring-alerts-6 qEAoSNpTRRyqO7fqAzwpeg 1 1 1 0 6.2kb 6.2kb
|
|
|
|
|
yellow open .triggered_watches 7g7_MGXFR7mBx0FwQzxpUg 1 1 0 0 48.1kb 48.1kb
|
|
|
|
|
yellow open .kibana HEQj4GnTQauN3HkwM8CPng 1 1 1 0 3.2kb 3.2kb
|
|
|
|
|
```
|
