Open PeterZh6 opened 9 hours ago
This exception will not leading to system malfunction. What problem do you want to solve?
This exception will not leading to system malfunction. What problem do you want to solve?
Thanks for your attention :)
Firstly, this exception keeps popping up once the manager container is started. It is not only annoying as it fills the screen with exception message, but also does contains unwanted behaviour as mentioned above.
Secondly, the configuration of data syncronization job fails immediately after it is approved, while this problem didn't exist on the 1.13.0 version of docker image. I am not sure whether I'm doing it right. It would be great if you could try to configure a data syncronization job with docker deployment of inlong personally and check whether this issue will cause the system to malfunction.
I am try to reproduce this example but encountered this issue.
What happened
Summary
When starting Inlong with Docker, the manager continuously throws an exception, leading to system malfunction. This issue was previously mentioned in Issue #11071. However, the associated PR only addressed a null check without resolving the core issue. Reopening this ticket for further investigation.
Description
After deploying Inlong with Docker, the manager produces the following error:
This error prevents the manager from functioning, rendering the entire system unusable.
Click to view complete log
Here is a screenshot explaining what's going on.
What you expected to happen
In version 1.13.0 of Inlong Docker, this issue does not occur. The latest version seems to introduce a change where the Inlong Agent module queries the
inlong_agent_system
group, which has not been created. This results in a request the manager cannot handle.Possible reasons of this issue
In PR #10757, a
Sender
object was introduced withgroup_id=INLONG_AGENT_SYSTEM
, created withDefaultMessageSender
. Within this setup:group_id=INLONG_AGENT_SYSTEM
is passed to theSender
constructor withProxyClientConfig
. TheSender
constructor will instantiateClientMgr
.ClientMgr
invokes thegetGroupIdConfigureInfo()
method, which likely triggers the root exception due to an attempt to request a configuration for the non-existentINLONG_AGENT_SYSTEM
group by callingrequestProxyList()
eventually.How to reproduce
docker/docker-compose
and followREADME.md
instructions.apache_inlong_manager.sql
andapache_inlong_audit_mysql.sql
into asql
directory underdocker/docker-compose
.docker-compose up -d
.docker exec -it manager
and inspectlogs/manager-all.log
, or use theLogs
option in Docker Desktop if available.Environment
WSL2 Ubuntu 22.04.4 LTS Docker Engine v25.0.3
InLong version
master
InLong Component
InLong Manager
Are you willing to submit PR?
Code of Conduct