如下，oceanbase数据库报这个正常么？
如下，oceanbase数据库报这个正常么？ob是 3.2.3.3 版本
---------------------------------------------------------------------------------------------------------------------------------+
[root@ocp-meta tmp]# cat ./check_report//check_report_observer_2024-01-26-09-27-18.table
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| warning-tasks-report |
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| task | task_report |
+-----------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| cluster.core_file_find | [warning] Unadapted by version. SKIP |
| cluster.data_path_settings | [warning] Unadapted by version. SKIP |
| cluster.deadlocks | [warning] Unadapted by version. SKIP |
| cluster.global_indexes_too_much | [warning] Unadapted by version. SKIP |
| cluster.major | [warning] Unadapted by version. SKIP |
| cluster.mod_too_large | [warning] Unadapted by version. SKIP
版权声明：本文内容由阿里云实名注册用户自发贡献，版权归原作者所有，阿里云开发者社区不拥有其著作权，亦不承担相应法律责任。具体规则请查看《阿里云开发者社区用户服务协议》和《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容，填写侵权投诉表单进行举报，一经查实，本社区将立刻删除涉嫌侵权内容。
-
看日志是提示参数值过高。后面的是推荐的参数值 obdiag目前的巡检依据是来自于内部的经验测试，部分虽然报错，如ulimit -n is 655360这个是符合日常运行的值，其他类型还是改下。巡检依据的来源是这里https://www.oceanbase.com/docs/common-obdiag-cn-1000000000493929 目前巡检对3.x的适配还不太行，我们这边会加紧补充—此回答来自钉群“[社区]技术答疑群OceanBase”
2024-01-30 14:15:04赞同 展开评论
