Closed ChairmanArthur closed 8 months ago
this is a known issue that the flink connector connects FE and FE returns a HTTP redirection with the internal address of the BE. you can make sure that http://e547433b93f1:8040
is reachable from outside the docker, (e.g., mapping the 8040 port to the host), and then try again. We will improve the allin1 docker to support this scenario.
您好,我是林恩伟,你发的邮件我已经收到。
I've received your email and will will reply to you as soon as possible after the vacation.————————————This is an auto reply email from QQ Mail.
您好,您的邮件已收到,我会尽快给你回复。
this is a known issue that the flink connector connects FE and FE returns a HTTP redirection with the internal address of the BE. you can make sure that
http://e547433b93f1:8040
is reachable from outside the docker, (e.g., mapping the 8040 port to the host), and then try again. We will improve the allin1 docker to support this scenario.
I tried verifying those ports already using telnet for 8030, 8040, and 8060, and they were all able to connect.
ajh@ajh-VirtualBox:~/flink-1.15.4$ telnet a22826981340 8030
Trying 192.168.1.19...
Connected to e547433b93f1.
ajh@ajh-VirtualBox:~/flink-1.15.4$ telnet a22826981340 8040
Trying 192.168.1.19...
Connected to e547433b93f1.
ajh@ajh-VirtualBox:~/flink-1.15.4$ telnet a22826981340 8060
Trying 192.168.1.19...
Connected to e547433b93f1.
The reason why it said connected to a different name is because of the way I modified etc/hosts, the two names points to the name ip address:
ajh@ajh-VirtualBox:~/flink-1.15.4$ sudo vim /etc/hosts
[sudo] password for ajh:
127.0.0.1 localhost
127.0.1.1 ajh-VirtualBox
192.168.1.19 e547433b93f1 a22826981340
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
~
~
~
~
~
~
~
~
~
~
~
~
~
"/etc/hosts" 10L, 268C 1,1 All
can you have a try with our formal release. starrocks/allin1-ubuntu:3.1.0
?
We have marked this issue as stale because it has been inactive for 6 months. If this issue is still relevant, removing the stale label or adding a comment will keep it active. Otherwise, we'll close it in 10 days to keep the issue queue tidy. Thank you for your contribution to StarRocks!
This was based on the following instructions: https://docs.starrocks.io/en-us/latest/unloading/Flink_connector
Instead of the StarRocks setup through VMs, I used the StarRocks allin1 on Docker instead, based on the following guide to set up and deploy StarRocks with Docker: https://docs.starrocks.io/en-us/latest/quick_start/deploy_with_docker
Instead of behaving as the expected behavior in the Flink connector guide, it returned several different errors after multiple attempts using different ports. I have already made sure to change and modify my etc/hosts file to include the IP and DNS names used for StarRocks allin1 as well before hands.
First it failed by trying connection with port 8030 on scan_url, which gave the following error:
8040 connection failed as well:
8060 gives the following issue:
Steps to reproduce the behavior
Expected behavior
The expected behavior of this would be as depicted on the guide, where data is successfully read from StarRocks using Flink SQL.
Real behavior
Instead of behaving as the expected behavior in the guide, it returned several different errors after multiple attempts using different ports.
First it failed by trying connection with port 8030 on scan_url, which gave the following error:
8040 connection failed as well:
8060 gives the following issue:
StarRocks version
The StarRocks version used here is 3.1.0-rc01-64ca37e863
Below are the code used on the Windows Command Prompt: