sling-cli icon indicating copy to clipboard operation
sling-cli copied to clipboard

Sling issue while inserting data into StarRocks using Parquet Format.

Open pawan-chauhan-9560 opened this issue 1 year ago • 3 comments

Issue Description

  • privateIp :- FE_Url
  • Description of the issue: Using a parquet file, 4125 events available. Getting dataflow issue dial tcp privateIP:8040: connect: connection refused

context canceled

  • Sling version 1.2.11

  • Operating System linux

  • Replication Configuration:

source:  Parquet file ( Created from sql server)
target: Starrocks
streams:
  ./sling run --src-stream 'file:///opt/sling/fastest/*.parquet' --tgt-conn STARROCKS --tgt-object testing.Product' --mode full-refresh
  • Log Output (please run command with -d):
~ could not perform request
Put "http://test:***@privateIP:8040/api/testing/FastestGrowingHSProducts_3_tmp/_stream_load": dial tcp **privateIP**:8040: connect: connection refused

context canceled

~ error writing dataflow to local storage: /tmp/starrocks/testing/Product_3_tmp/2024-06-17T083727.126
~ could not perform request
Put "http://test:***@privateIP:8040/api/testing/Product_3_tmp/_stream_load": dial tcp **privateIP**:8040: connect: connection refused

pawan-chauhan-9560 avatar Jun 17 '24 06:06 pawan-chauhan-9560

hi, this seems like it's an issue with your connection. Can you specify the fe_url? if there is a user/password, specify in url correctly (http://myuser:[email protected]:8030) See docs: https://docs.slingdata.io/connections/database-connections/starrocks also make sure sling conns test Starrocks works.

flarco avatar Jun 17 '24 12:06 flarco

Added the user and password but getting same issue

~ could not perform request Put "http://test:***@192.168.191.1:8040/api/testing/FastestGrowingHSProducts_3_tmp/_stream_load": dial tcp 192.168.191.1:8040: connect: connection refused

pawan-chauhan-9560 avatar Jun 19 '24 14:06 pawan-chauhan-9560

That's strange. Since I can't reproduce this, it's hard to tackle. I would suggest trying to load into your instance via the curl command to see if you're getting that error. connection refused means something is wrong with either your hostname/port Please ensure your fe_url is correct, including the scheme.

flarco avatar Jun 19 '24 21:06 flarco