Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Download sst return success but actually failed #4321

Closed
dbacyj opened this issue Jun 14, 2022 · 6 comments · Fixed by #4442
Closed

Download sst return success but actually failed #4321

dbacyj opened this issue Jun 14, 2022 · 6 comments · Fixed by #4442
Assignees
Labels
priority/low-pri Priority: low severity/minor Severity of bug type/bug Type: something is unexpected
Milestone

Comments

@dbacyj
Copy link
Contributor

dbacyj commented Jun 14, 2022

Describe the bug (required)
As title

Your Environments (required)

  • Commit id (e.g. a3ffc7d8)
    image

How To Reproduce(required)

Steps to reproduce the behavior:

image

image

image

Expected behavior

Additional context

@dbacyj dbacyj added the type/bug Type: something is unexpected label Jun 14, 2022
@dbacyj dbacyj changed the title Download sst Download sst return success but Jun 14, 2022
@dbacyj dbacyj changed the title Download sst return success but Download sst return success but actually failed Jun 14, 2022
@dbacyj
Copy link
Contributor Author

dbacyj commented Jun 14, 2022

The reason the download fails is that the port should be 9000 not 9090

@critical27
Copy link
Contributor

How can we tell 9090 is not a correct hdfs port? User should be responsible for what he inputs to nebula.

@critical27
Copy link
Contributor

critical27 commented Jul 19, 2022

And btw, the log above means that it truly succeed to download from 9090 (Otherwise, it will print error log).

I'll close it for now. Could reopen it if you have different opinions.

@dbacyj
Copy link
Contributor Author

dbacyj commented Jul 19, 2022

The port number is just to supplement the reason for the failure, the point is that it actually failed, but returned success. Here we can't get the actual success status, right?

@critical27
Copy link
Contributor

Yeah, can't get status. Probably same as #4382. Not sure if we can address it, will try.

@critical27
Copy link
Contributor

Could try it after #4442 merged @dbacyj. If the hdfs address is illegal, it will return a error. But I don't have the hdfs environment, so it has not been totally verified when the address is legal.

@critical27 critical27 reopened this Jul 19, 2022
@jinyingsunny jinyingsunny added duplicate Solution: this issue or pull request already exists severity/minor Severity of bug and removed duplicate Solution: this issue or pull request already exists labels Nov 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/low-pri Priority: low severity/minor Severity of bug type/bug Type: something is unexpected
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants