Failed to get peer address
- Dominant language
- C
- Stars
- 1.5k
- Forks
- 243
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 37
Description
I am trying to run TPCH benchmarks on Comdb2. And calling .execute("DELETE FROM Customer") I encountered the following errors. What should I do to solve this?
[java] at com.bloomberg.comdb2.jdbc.SockIO.open(SockIO.java:130)
[java] at com.bloomberg.comdb2.jdbc.SockIO.write(SockIO.java:73)
[java] at com.bloomberg.comdb2.jdbc.SockIO.write(SockIO.java:81)
[java] at com.bloomberg.comdb2.jdbc.Comdb2Handle.reopen(Comdb2Handle.java:1795)
[java] at com.bloomberg.comdb2.jdbc.Comdb2Handle.open(Comdb2Handle.java:1618)
[java] at com.bloomberg.comdb2.jdbc.Comdb2Handle.runStatementInt(Comdb2Handle.java:911)
[java] at com.bloomberg.comdb2.jdbc.Comdb2Handle.runStatement(Comdb2Handle.java:1342)
[java] at com.bloomberg.comdb2.jdbc.Comdb2Handle.runStatement(Comdb2Handle.java:751)
[java] at com.bloomberg.comdb2.jdbc.Comdb2Statement.executeQuery(Comdb2Statement.java:118)
[java] at com.bloomberg.comdb2.jdbc.Comdb2Statement.executeQuery(Comdb2Statement.java:70)
[java] at com.bloomberg.comdb2.jdbc.Comdb2Statement.execute(Comdb2Statement.java:232)
2017/12/13 22:01:30 [ERROR] accept_thread: timeout reading from socket, peeraddr=127.0.0.1
2017/12/13 22:01:30 [ERROR] accept_thread: timeout reading from socket, peeraddr=127.0.0.1
2017/12/13 22:01:30 [ERROR] accept_thread: timeout reading from socket, peeraddr=127.0.0.1
2017/12/13 22:01:30 [ERROR] accept_thread: timeout reading from socket, peeraddr=127.0.0.1
clnt is 0x6862b10, sql is begin
2017/12/13 22:01:30 [ERROR] read_newsql_query: Invalid message 1852143475
2017/12/13 22:01:30 [ERROR] accept_thread: timeout reading from socket, peeraddr=127.0.0.1
2017/12/13 22:01:30 [ERROR] Failed to get peer address
Contributor guide
Research direction
Start with the JDBC stack at comdb2.jdbc.SockIO.open (SockIO.java:130), then trace the server messages from accept_thread through read_newsql_query. Reproduce the TPCH DELETE request and compare the client trace with the peer-address and invalid-message errors; done means the failure's cause is identified and the behavior is corrected or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, java, sql
- Domain
- backend, databases, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100