You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@doris.apache.org by "liangjw (via GitHub)" <gi...@apache.org> on 2023/06/14 01:12:20 UTC
[GitHub] [doris] liangjw opened a new issue, #20772: [Bug] A large amount of 'apply filter meet error' occurred during the Doris BE running process and the node subsequently crashed
liangjw opened a new issue, #20772:
URL: https://github.com/apache/doris/issues/20772
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no similar issues.
### Version
1.1.4
### What's Wrong?
W0614 07:54:09.901906 21932 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da3620374d
W0614 07:54:09.902081 21934 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da36203751
W0614 07:54:09.940635 21952 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da3620376d
W0614 07:54:09.941871 21948 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da36203769
W0614 07:54:10.075472 21935 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da3620308d
W0614 07:54:10.106557 21938 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da36203071
W0614 07:54:10.106801 21945 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da362030a5
W0614 07:54:11.370494 21948 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da36202f88
W0614 07:54:11.371394 21930 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da36202efc
W0614 07:54:11.371764 21931 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da36202fbc
W0614 07:54:11.384529 21934 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da36202dd8
W0614 07:54:11.391996 21945 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da36202f18
W0614 07:54:11.437300 21933 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da36202d30
W0614 07:54:11.444432 21935 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da36202d64
W0614 07:54:11.610685 21937 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da36202d4c
W0614 07:54:12.464573 21930 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da36202c40
W0614 07:54:12.479187 21948 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da36202c0c
W0614 07:54:12.481343 21953 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da36202c28
W0614 07:54:12.482730 21954 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da36202bf0
W0614 07:54:16.794438 21947 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da362035c5
W0614 07:54:16.900700 26991 runtime_filter_rpc.cpp:95] runtimefilter rpc err:[E1008]Reached timeout=1000ms @XXXXX:8060
W0614 07:54:16.913249 29079 runtime_filter_rpc.cpp:95] runtimefilter rpc err:[E1008]Reached timeout=1000ms @XXXX:8060
W0614 07:54:16.932248 21936 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da3620345d
W0614 07:54:16.933837 24579 runtime_filter_rpc.cpp:95] runtimefilter rpc err:[E1008]Reached timeout=1000ms @XXXXX:8060
W0614 07:54:16.939539 21934 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da36202ff8
W0614 07:54:16.959442 21931 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da36203205
W0614 07:54:16.979343 21945 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da3620384d
W0614 07:54:16.999042 21929 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da362036f5
W0614 07:54:17.095525 21952 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da36202da0
W0614 07:54:17.134732 28826 runtime_filter_rpc.cpp:95] runtimefilter rpc err:[E1008]Reached timeout=1000ms @XXXXXX:8060
W0614 07:54:17.163506 21948 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da36202bb3
W0614 07:54:17.254422 21953 internal_service.cpp:463] apply filter meet error: Invalid argument: fragment-id: 3c8cee8e4cde43e5-ad57c7da3620295b
A large amount of 'apply filter meet error' occurred during the Doris BE running process and the node subsequently crashed.
Can not find any detail logs anymore.
### What You Expected?
Figure out why this error occurred.
### How to Reproduce?
_No response_
### Anything Else?
_No response_
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org
For additional commands, e-mail: commits-help@doris.apache.org
[GitHub] [doris] somnmos commented on issue #20772: [Bug] A large amount of 'apply filter meet error' occurred during the Doris BE running process and the node subsequently crashed
Posted by "somnmos (via GitHub)" <gi...@apache.org>.
somnmos commented on issue #20772:
URL: https://github.com/apache/doris/issues/20772#issuecomment-1672409206
Version：1.1.5
I meet the same issue, but i couldn’t found the cause. Even though i restart the BE, BE still crashed when i execute sql.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org
For additional commands, e-mail: commits-help@doris.apache.org
[GitHub] [doris] wuyunzzz commented on issue #20772: [Bug] A large amount of 'apply filter meet error' occurred during the Doris BE running process and the node subsequently crashed
Posted by "wuyunzzz (via GitHub)" <gi...@apache.org>.
wuyunzzz commented on issue #20772:
URL: https://github.com/apache/doris/issues/20772#issuecomment-1649041144
I'm also having this issue. When I restart the backends, it's ok. how did you solve it?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@doris.apache.org
For additional commands, e-mail: commits-help@doris.apache.org