Error in viewing collection information when there is a schedule with more than a certain number of collections in the database menu.

[ian-lss]

Describe the bug:
When there are more than 4-5 collections, as shown in the picture, an error appears in the status, and the information is not displayed when auto-refresh occurs or when the refresh button is clicked.
Milvus is in a normal state, and refreshing the browser displays correctly until the next auto-refresh.

Steps to reproduce:

1. login
2. database menu click
3. Create more than 7 collections and load data into them.
4. Wait for auto-refresh or continuously click the refresh button.

Attu version:
2.4.2

Milvus version:
2.4.4

[shanghaikid]

Thanks, I will test it later.

[shanghaikid]

That is strange. I can not reproduce this.

Maybe there is a status that I don't know, so I made a change, it the status is not unloaded/loading/loaded, just show it directly other than showing error. I will keep testing it.

[ian-lss]

@shanghaikid
Hello,

To assist with the verification, I am attaching a video.
It is the collection list page of the Database.
Due to internal security, we are unable to share the entire page; we appreciate your understanding.

When the page first loads, everything appears normal.
However, after auto-refresh, some information in the collection list is not visible.
Looking at the collection details that are not visible, the status is marked as “error,” as shown in the attached picture. There were no issues with auto-refresh when there were up to 3-4 collections.

What is particularly notable is that the collection order is inconsistent with each refresh, and it is always the bottom three collections that do not display information.
You can see that the order is inconsistent by checking the approx Count in the video.
https://github.com/zilliztech/attu/assets/38341885/d4fa4e33-fd40-4a25-9658-883d8820ba16

[shanghaikid]

I will test it with your condition.

[shanghaikid]

I've created 31 collections, here is my test.
https://github.com/zilliztech/attu/assets/185051/aedbee6b-8079-4bc3-9f8e-745e76ed0beb

Since the information needed for the page comes from multiple APIs, I retrieve it in batches of five collections at a time.

I sort collections by loadedPercentage and if it has index or not, then createdTime.

Which order do you prefer?

[ian-lss]

@shanghaikid
Sorry for the delayed response as I was testing various things.
As a result, I was able to reproduce the issue without much difficulty.
It seems to be unrelated to the number of data entries, dimensions, etc.

One difference between your video and my situation is that you clicked the Refresh button to refresh, whereas I waited for the auto-refresh.
Under normal circumstances, continuously clicking the refresh button doesn’t cause any issues.
However, after an auto-refresh that leads to an incorrect state, clicking the refresh button does not restore the list to normal, and the page needs to be fully reloaded to return to a normal state. Below is the video of the test.

20240625_142258.mp4

As you may know, the auto-refresh interval is quite long (1 minute? 2 minutes?).
Please understand that since the video was recorded some time after the initial situation, it might seem like the auto-refresh interval is very short.

The data was generated using the insert sample data feature in attu, with the schema consisting of only an auto_id field and a vector field.
The index type is HNSW, and the index options were configured to the maximum extent possible.
I tested both dimensions 1536 and 128, and both resulted in the same issue.
The Dynamic Schema option was applied to only some collections, and the consistency was set to Bounded for some and Strong for others.

Additionally, when the dimension is large (e.g., OpenAI dimension 1536), an error occurs when inserting 10k entries of sample data, as shown below.
However, this is an attu error, not a Milvus error. After the error occurs, if you refresh again, the screen appears normal after a while.
It seems that the system hangs while bulk inserting data into Milvus, and once the insert is complete, it returns to normal.

And like in most databases when displaying names, alphabetical order is preferred.