thebalu edited a comment on pull request #95:
URL: https://github.com/apache/bahir-flink/pull/95#issuecomment-682031424


   I've been looking into it a bit, but I am not too familiar with Docker / 
TestContainers.
   
   So the `localhost:32799` (port is always random) comes from this line:
   `masterAddress = HostAndPort.fromParts(master.getContainerIpAddress(), 
master.getMappedPort(KUDU_MASTER_PORT)).toString();`
   
   `master.getHost()` returns localhost as well.
   
   The containers get successfully created in the `beforeClass`, I am able to 
see the logs inside the master container (but not in the tserver containers).
   It seems that at some point after a request is received (I can see the 
CreateTableRequest in the master logs), there is a communication error between 
the master and tservers, and all containers crash/terminate. I wasn't able to 
recover their full logs afterwards, but these lines appear not long before the 
crash in the master container:
   ```
   I0827 15:29:30.977533   134 catalog_manager.cc:4136] T 
9af663be017b44d188234a7cb11d7d32 P 534ed6b36ec04fb5b19a012b196dd36b reported 
cstate change: term changed from 0 to 1, leader changed from <none> to 
534ed6b36ec04fb5b19a012b196dd36b (192.168.80.5). New cstate: current_term: 1 
leader_uuid: "534ed6b36ec04fb5b19a012b196dd36b" committed_config { opid_index: 
-1 OBSOLETE_local: true peers { permanent_uuid: 
"534ed6b36ec04fb5b19a012b196dd36b" member_type: VOTER last_known_addr { host: 
"192.168.80.5" port: 7050 } health_report { overall_health: HEALTHY } } }
   I0827 15:29:30.981220   134 catalog_manager.cc:4136] T 
38d2fb973558459e9150354ceee68d72 P df98f3e17885477595190ba2dab55530 reported 
cstate change: term changed from 0 to 1, leader changed from <none> to 
df98f3e17885477595190ba2dab55530 (192.168.80.3). New cstate: current_term: 1 
leader_uuid: "df98f3e17885477595190ba2dab55530" committed_config { opid_index: 
-1 OBSOLETE_local: true peers { permanent_uuid: 
"df98f3e17885477595190ba2dab55530" member_type: VOTER last_known_addr { host: 
"192.168.80.3" port: 7050 } health_report { overall_health: HEALTHY } } }
   W0827 15:30:01.096755   117 connection.cc:655] server connection from 
192.168.80.5:44398 recv error: Network error: failed to read from TLS socket 
(remote: 192.168.80.5:44398): Connection reset by peer (error 104)
   W0827 15:30:01.097028   114 connection.cc:655] client connection to 
192.168.80.5:7050 recv error: Network error: failed to read from TLS socket 
(remote: 192.168.80.5:7050): Connection reset by peer (error 104)
   W0827 15:30:01.342813   115 connection.cc:655] server connection from 
192.168.80.4:48140 recv error: Network error: failed to read from TLS socket 
(remote: 192.168.80.4:48140): Connection reset by peer (error 104)
   ```
   
   @bsideup Do you mean starting the kudu containers manually with docker run, 
and hardcoding their ports in the test? 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to