-
Notifications
You must be signed in to change notification settings - Fork 77
Table 'milvus_meta.collections' doesn't exist #420
Comments
looks like the script failed to create table in the DB. https://github.com/milvus-io/milvus/blob/master/tests/scripts/values/mysql.yaml @NicoYuan1986 could you please help take a look at this one? |
@xyfleet You need manually provision a mysql database with tables first. |
@LoveEachDay Thank you so much. I added these tables manually. Then I met another issue. In rootcood pod:
In DataCoord pod:
In querycood pod, proxy pod, datanode pod:
In querycood pod:
In the same time, I see some errors from etcd pod and zookeeper. errors from etcd:
one zookeeper:
I think something is wrong with my etcd and kafka-zookeeper setting. Not sure if this is the reason why milvus pods still failed? About the etcd and zookeeper errors, do you have any ideas? About the external s3 and kafka, please help check if there is an issue:
|
@LoveEachDay Today, I reconfigured the kafka, zookeeper and etcd. Still get the same error. Logs attached. Thanks. |
@xyfleet From the provided log:
The config for |
@LoveEachDay Thanks a lot. The host, you mean something like this |
@xyfleet and also set |
Yes
|
@LoveEachDay I tried several times, still get this error
I tried two different s3 accounts but got the same error. I think my s3-user has right permission. Do you have any idea? s3-user permission:
externals3 config:
|
@xyfleet Sry, my mistake. Milvus uses url path to access bucket, it doesn't support it by host. You can change your |
@haorenfsa Thanks for your update. I updated my code and still got error. Really weird.
I found this python code, https://github.com/milvus-io/milvus/blob/master/tests/benchmark/milvus_benchmark/update.py,
|
@haorenfsa Do you think we can have a quick zoom meeting to troubleshoot this one? |
@xyfleet Could you join the slack channel?
|
Hi Team,
I met this error log below in the pod of rootcoord. As a result, the rootcoord pod is in standby mode.
But from the log, I can see the connection to the external mysql DB is good.
Then, all of the related pods, datanode pod, querycoord pod, proxy pod, indexcoord pod are all in WaitForComponentStates
Background:
I am using an external mysql when I install this chart.
Below is part of my value.yaml
One more question here, I did not enable profiling in each component. Is this a problem?
Any help will be appreciated.
The text was updated successfully, but these errors were encountered: