Is there a bug in v0.8.32 that it doesn't show up ...
# troubleshoot
b
Is there a bug in v0.8.32 that it doesn't show up in the search results? I can see the dataset in
http://{datahub-frontend_url}/browse
but not in
http://{datahub-frontend_url}/search
.
b
were you able to search for any dataset that was ingested recently? i had a similar experience recently https://datahubspace.slack.com/archives/C029A3M079U/p1648792489850339
b
I think it's probably the same phenomenon. 😥
Often in the past, docker-compose up would not start the broker and I would have to delete the docker_broker volume once to get it to start. It's somewhat troublesome to have to run docker-compose down and delete the volume every time I ingest new datasets.
b
@early-lamp-41924 for awareness
b
After more than 30 minutes of ingest, I can see the ingested datasets even from /search.
When I access the Entity page, I get "An unknown error occurred (code 500)" and no data is displayed.
The following steps have been taken to recover. 1. docker-compose down 2. docker volume rm docker_broker 3. docker-compose p -d
e
Just getting on this one. Hmn since browse is updated the MCL events are getting to the consumers but it is stopping midway? Super weird that you have to remove broker volume to solve this issue
We had a recent PR that got shipped to add this broker volume
Thought that would have no effect whatsoever, but seems like it has some side effects