Skip to content

dolphinscheduler A problem occurred when I tried the last 200M file in the Content Center #13580

@TheWindIsRising

Description

@TheWindIsRising

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

I am the dolphinscheduler deployed by Kubernetes
The last time I tried to create a file of more than 200 megabytes in the resource center, the page did not respond after more than ten seconds. When I went to check the log, I found an error message
1676686913268
[WARN] 2023-02-18 10:15:41.073 +0800 org.springframework.web.servlet.mvc.method.annotation.ExceptionHandlerExceptionResolver:[434] - Failure in @ExceptionHandler org.apache.dolphinscheduler.api.exceptions.ApiExceptionHandler#exceptionHandler(Exception, HandlerMethod)
java.lang.IllegalStateException: Could not resolve parameter [1] in public org.apache.dolphinscheduler.api.utils.Result org.apache.dolphinscheduler.api.exceptions.ApiExceptionHandler.exceptionHandler(java.lang.Exception,org.springframework.web.method.HandlerMethod): No suitable resolver

What you expected to happen

I checked the relevant configuration file api-server/conf/application.yaml. The default value is to meet my upload requirements

How to reproduce

The last time I tried to create a file of more than 200 megabytes in the resource center, the page did not respond after more than ten seconds. When I went to check the log, I found an error message
1676686913268
[WARN] 2023-02-18 10:15:41.073 +0800 org.springframework.web.servlet.mvc.method.annotation.ExceptionHandlerExceptionResolver:[434] - Failure in @ExceptionHandler org.apache.dolphinscheduler.api.exceptions.ApiExceptionHandler#exceptionHandler(Exception, HandlerMethod)
java.lang.IllegalStateException: Could not resolve parameter [1] in public org.apache.dolphinscheduler.api.utils.Result org.apache.dolphinscheduler.api.exceptions.ApiExceptionHandler.exceptionHandler(java.lang.Exception,org.springframework.web.method.HandlerMethod): No suitable resolver

Anything else

No response

Version

3.1.x

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingduplicateThis issue or pull request already exists

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions