Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: flush timeout after upgrading from v2.3.4 to 2.4-20240517-780f3137-amd64 #33149

Closed
1 task done
zhuwenxing opened this issue May 20, 2024 · 5 comments
Closed
1 task done
Assignees
Labels
kind/bug Issues or changes related a bug priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. severity/critical Critical, lead to crash, data missing, wrong result, function totally doesn't work. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@zhuwenxing
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:v2.3.4 --> 2.4-20240517-780f3137-amd64
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior


[2024-05-19T09:03:29.864Z] [2024-05-19 08:59:19 - INFO - ci_test]: *********************************** setup *********************************** (client_base.py:44)

[2024-05-19T09:03:29.864Z] [2024-05-19 08:59:19 - INFO - ci_test]: [setup_method] Start setup test case test_milvus_default. (client_base.py:45)

[2024-05-19T09:03:29.864Z] ------------------------------ Captured log call -------------------------------

[2024-05-19T09:03:29.864Z] [2024-05-19 08:59:19 - DEBUG - ci_test]: (api_request)  : [Connections.connect] args: ['default', '', '', 'default', ''], kwargs: {'host': '10.255.168.95', 'port': 19530} (api_request.py:62)

[2024-05-19T09:03:29.864Z] [2024-05-19 08:59:19 - DEBUG - ci_test]: (api_response) : None  (api_request.py:37)

[2024-05-19T09:03:29.864Z] [2024-05-19 08:59:19 - DEBUG - ci_test]: (api_request)  : [Connections.has_connection] args: ['default'], kwargs: {} (api_request.py:62)

[2024-05-19T09:03:29.864Z] [2024-05-19 08:59:19 - DEBUG - ci_test]: (api_response) : True  (api_request.py:37)

[2024-05-19T09:03:29.865Z] [2024-05-19 08:59:19 - DEBUG - ci_test]: (api_request)  : [Collection] args: ['InsertChecker__ypf3ooxY', {'auto_id': False, 'description': '', 'fields': [{'name': 'int64', 'description': '', 'type': <DataType.INT64: 5>, 'is_primary': True, 'auto_id': False}, {'name': 'float', 'description': '', 'type': <DataType.FLOAT: 10>}, {'name': 'varchar', 'description': '', 'type': <Da......, kwargs: {'consistency_level': 'Strong'} (api_request.py:62)

[2024-05-19T09:03:29.865Z] [2024-05-19 08:59:19 - DEBUG - ci_test]: (api_response) : <Collection>:

[2024-05-19T09:03:29.865Z] -------------

[2024-05-19T09:03:29.865Z] <name>: InsertChecker__ypf3ooxY

[2024-05-19T09:03:29.865Z] <description>: 

[2024-05-19T09:03:29.865Z] <schema>: {'auto_id': False, 'description': '', 'fields': [{'name': 'int64', 'description': '', 'type': <DataType.INT64: 5>, 'is_primary': True, 'auto_id': False}, {'name': 'float', 'description': '', 'type': <DataType.FLOAT......  (api_request.py:37)

[2024-05-19T09:03:29.865Z] [2024-05-19 08:59:19 - DEBUG - ci_test]: (api_request)  : [Collection.flush] args: [], kwargs: {'timeout': 180} (api_request.py:62)

[2024-05-19T09:03:29.865Z] ________ TestAllCollection.test_milvus_default[IndexChecker__4sQfFU0R] _________

[2024-05-19T09:03:29.865Z] [gw2] linux -- Python 3.8.10 /usr/bin/python3.8

[2024-05-19T09:03:29.865Z] 

[2024-05-19T09:03:29.865Z] self = <test_all_collections_after_chaos.TestAllCollection object at 0x7fc4215e7a90>

[2024-05-19T09:03:29.865Z] collection_name = 'IndexChecker__4sQfFU0R'

[2024-05-19T09:03:29.865Z] 

[2024-05-19T09:03:29.865Z]     @pytest.mark.tags(CaseLabel.L1)

[2024-05-19T09:03:29.865Z]     def test_milvus_default(self, collection_name):

[2024-05-19T09:03:29.865Z]         self._connect()

[2024-05-19T09:03:29.865Z]         # create

[2024-05-19T09:03:29.865Z]         name = collection_name if collection_name else cf.gen_unique_str("Checker_")

[2024-05-19T09:03:29.865Z]         t0 = time.time()

[2024-05-19T09:03:29.865Z]         schema = Collection(name=name).schema

[2024-05-19T09:03:29.865Z]         collection_w = self.init_collection_wrap(name=name, schema=schema)

[2024-05-19T09:03:29.865Z]         tt = time.time() - t0

[2024-05-19T09:03:29.865Z]         assert collection_w.name == name

[2024-05-19T09:03:29.865Z]         # get collection info

[2024-05-19T09:03:29.865Z]         schema = collection_w.schema

[2024-05-19T09:03:29.865Z]         dim = cf.get_dim_by_schema(schema=schema)

[2024-05-19T09:03:29.865Z]         int64_field_name = cf.get_int64_field_name(schema=schema)

[2024-05-19T09:03:29.865Z]         float_vector_field_name = cf.get_float_vec_field_name(schema=schema)

[2024-05-19T09:03:29.865Z]         float_vector_field_name_list = cf.get_float_vec_field_name_list(schema=schema)

[2024-05-19T09:03:29.865Z]         # compact collection before getting num_entities

[2024-05-19T09:03:29.865Z] >       collection_w.flush(timeout=180)

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

failed job: https://qa-jenkins.milvus.io/blue/organizations/jenkins/deploy_test_for_release_cron/detail/deploy_test_for_release_cron/1811/pipeline

log:
artifacts-pulsar-cluster-upgrade-1811-server-logs.tar.gz

Anything else?

No response

@zhuwenxing zhuwenxing added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 20, 2024
@zhuwenxing zhuwenxing added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. severity/critical Critical, lead to crash, data missing, wrong result, function totally doesn't work. labels May 20, 2024
@XuanYang-cn
Copy link
Contributor

/assign

@yanliang567 yanliang567 added this to the 2.4.2 milestone May 20, 2024
@yanliang567 yanliang567 added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 20, 2024
@yanliang567 yanliang567 removed their assignment May 20, 2024
@XuanYang-cn
Copy link
Contributor

@zhuwenxing is v2.3.4 are way too old, please use v2.3.15 later when PR's ready

sre-ci-robot pushed a commit that referenced this issue May 22, 2024
See also: #33151, #33149

---------

Signed-off-by: yangxuan <xuan.yang@zilliz.com>
XuanYang-cn added a commit to XuanYang-cn/milvus that referenced this issue May 22, 2024
@XuanYang-cn
Copy link
Contributor

sre-ci-robot pushed a commit that referenced this issue May 22, 2024
See also: #33151, #33149
pr: #33193

Signed-off-by: yangxuan <xuan.yang@zilliz.com>
@XuanYang-cn
Copy link
Contributor

/assign @zhuwenxing
Please help verify

@zhuwenxing
Copy link
Contributor Author

verified and fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. severity/critical Critical, lead to crash, data missing, wrong result, function totally doesn't work. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants