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.

Sign up for GitHub

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

Jump to bottom

Dgraph alpha logs misinform connection to zero #4298

Closed
prashant-shahi opened this issue Nov 20, 2019 · 0 comments · Fixed by #4303
Closed

Dgraph alpha logs misinform connection to zero #4298

prashant-shahi opened this issue Nov 20, 2019 · 0 comments · Fixed by #4303
Labels
area/operations Related to operational aspects of the DB, including signals, flags, env vars, etc. area/usability Issues with usability and error messages exp/beginner Something most people could solve. kind/enhancement Something could be better. priority/P2 Somehow important but would not block a release. status/accepted We accept to investigate/work on it.

Comments

@prashant-shahi
Copy link
Contributor

prashant-shahi commented Nov 20, 2019 •
edited
Loading

What version of Dgraph are you using?

master

Steps to reproduce the issue (command/config used to run Dgraph).

Run alpha without running zero.

dgraph alpha

Result:

...
I1120 17:32:29.538152   14635 run.go:417] gRPC server started.  Listening on port 9080
I1120 17:32:29.538172   14635 run.go:418] HTTP server started.  Listening on port 8080
I1120 17:32:29.538234   14635 worker.go:81] Worker listening at address: [::]:7080
I1120 17:32:29.638517   14635 pool.go:148] CONNECTED to localhost:5080
W1120 17:32:29.640220   14635 pool.go:238] Connection lost with localhost:5080. Error: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:5080: connect: connection refused"

Expected:

Logs should not say CONNECTED to localhost:5080 but should inform connecting to localhost:5080 instead and upon successful connection print the success message.

cc: @mangalaman93
@danielmai danielmai added area/operations Related to operational aspects of the DB, including signals, flags, env vars, etc. area/usability Issues with usability and error messages exp/beginner Something most people could solve. kind/enhancement Something could be better. priority/P2 Somehow important but would not block a release. status/accepted We accept to investigate/work on it. labels Nov 20, 2019
fristonio added a commit to fristonio/dgraph that referenced this issue Nov 21, 2019
@fristonio
chore: fix connection log information in dgraph alpha
4895a92 
* Fixes dgraph-io#4298

Signed-off-by: Deepesh Pathak <[email protected]>
@fristonio fristonio mentioned this issue Nov 21, 2019
Merged
martinmr pushed a commit that referenced this issue Nov 21, 2019
@fristonio @martinmr
chore: fix connection log information in dgraph alpha (#4303)
8c97188 
* Fixes #4298

Signed-off-by: Deepesh Pathak <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/operations Related to operational aspects of the DB, including signals, flags, env vars, etc. area/usability Issues with usability and error messages exp/beginner Something most people could solve. kind/enhancement Something could be better. priority/P2 Somehow important but would not block a release. status/accepted We accept to investigate/work on it.
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: fix connection log information in dgraph alpha fristonio/dgraph
2 participants
@danielmai @prashant-shahi