-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Alias的错误处理:减少抛出大量object not found日志 #4054
Labels
bug
Something isn't working
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
我这边好像测试没有问题了 |
那我清掉数据开始再重测一下,再看看有没有方法把运行实例的log挂出来 |
This comment was marked as outdated.
This comment was marked as outdated.
我发现了 不太好处理这个问题 不是直接调用的日志而是间接调用导致的。 |
看错了 是list函数中也有个日志。。 |
xhofe
added a commit
that referenced
this issue
Apr 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please make sure of the following things
alist
and not something else(such asDependencies
orOperational
).Alist Version / Alist 版本
v3.15.0
Driver used / 使用的存储驱动
Alias
Describe the bug / 问题描述
感谢 #301756b 实现的别名功能,以下提的这或许不能算Bug,但想询问可否替换为更好的做法。
在访问别名目录时,对于文件结构不完全相同的网盘,会抛出大量的Object Not Found Error,使得log日志大量增长。可否忽略对应Error,或重定义此Error的输出。
举例说明,我的内容分别存储在5个盘上,这5个盘拥有着统一的文件结构,一级目录下共有12个分类
但并不是每个盘都有12个文件夹,比如最新的分类“012编曲”,只有一个盘有,则访问“012编曲”时,会因为在其余4个盘都找不到“012编曲”而抛出4个完整的objNotFound错误。这个问题在存具体资源的子文件夹上更加容易触发。
在对Alias文件夹建立索引时,对目录手动建立4级索引,一共1300个文件,由于连续抛出Not Found 错误,该次索引的导致日志文件增加了300K。在实际使用Alias统一整理多盘的目录时,5个小时左右的时间我不停访问别名的路径,产生了近80M的日志。其中还有包括自动索引无法停止build带来的连续日志增长(目前还没查明原因),但是大部分内容是由于访问别名目录不停抛出错误带来的。
从语义上来说,Alias合并目录时找不到对应文件不是Error,并且大量输出带来的错误日志增长已经影响到了对日常错误日志的排查。希望能有更好的解决方式,比如忽略别名合并路径时带来的object not found error,或改为info/warn提示“聚合x个路径,x个未找到”这样
Reproduction / 复现链接
私人链接不便公开,且主要是后端问题,非前端问题
Logs / 日志
The text was updated successfully, but these errors were encountered: