After upgrade to 3.5.7 (and 4.0.0): Error 1064 (HY000): Socket is closed by peer

[svdimchenko]

I start receiving such error after upgrading from SR 3.5.6 to 3.5.7 and the same error with 4.0.0 version. I can not find the issue in sql queries logs.

[chris-celerdata]

Can you share an reproducible example of this? I am able to run the test cases and local models with StarRocks version 4.0.0.

[svdimchenko]

Can you share an reproducible example of this? I am able to run the test cases and local models with StarRocks version 4.0.0.

somehow it reproduces on one env only with following error in fe.log

 com.starrocks.sql.analyzer.SemanticException: Getting analyzing error. Detail message: Unknown user: starrocks.dwh.dbt.
	at com.starrocks.authentication.AuthenticationMgr.getUserProperty(AuthenticationMgr.java:528)
	at com.starrocks.qe.ConnectProcessor.proxyExecute(ConnectProcessor.java:824)
	at com.starrocks.service.FrontendServiceImpl.forward(FrontendServiceImpl.java:1040)
	at com.starrocks.thrift.FrontendService$Processor$forward.getResult(FrontendService.java:5961)
	at com.starrocks.thrift.FrontendService$Processor$forward.getResult(FrontendService.java:5938)
	at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:40)
	at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:40)
	at com.starrocks.common.SRTThreadPoolServer$WorkerProcess.run(SRTThreadPoolServer.java:311)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:840)

here is model example

{{
    config(
        materialized="table",
        table_type="DUPLICATE",
        keys=["id"],
        distributed_by=["id"],
        partition_type="",
        engine="OLAP",
        properties={
            "replication_num": "3",
        },
    )
}}

select
    1 as id
    , 'x' as name
from {{ source("glue__d", "some_model") }}
limit 10

I use Ranger + LDAP integration for security for more context.

@chris-celerdata could you advice what can go wrong with that ?

Setting user to root resolves the issue. However just rollback to 3.5.6 version resolves the issue as well.

[chris-celerdata]

It looks like an authentication issue based on Unknown user: starrocks.dwh.dbt. I was not using Ranger or LDAP for security so that seems to the be the key difference. I'll do some more local tests on that.

[jaogoy]

There should be a bug for the integration with Ranger + LDAP in StarRocks, we will try to fix it.

[HangyuanLiu]

https://github.com/StarRocks/starrocks/pull/65929