It might be related to your local changes. This caught my eye: extra_master_flags: "--rpc_max_message_size=3860733440" extra_tserver_flags: "--rpc_max_message_size=3860733440"
Why did you have to add this configuration? What happens if you remove it? On a related note, do the tests still fail if you rebuild from a clean working tree (i.e. without your patches)? On Sat, Apr 13, 2019 at 12:52 PM Clemens Valiente <[email protected]> wrote: > > Hi, > > I have a few fixes for the kudu-mapreduce package and wanted to add unit > tests but neither the existing nor the newly added unit tests can be run on > my system. > > I managed to build kudu and theMiniKuduCluster starts up but then fails with > connection/timeout issues. > > I think this might point at the problem: > > 16:42:05.780 [INFO - cluster stderr printer] (MiniKuduCluster.java:543) 0410 > 16:42:05.779084 (+3053866us) negotiation.cc:304] Negotiation complete: Timed > out: Server connection negotiation failed: server connection from > 127.0.0.1:60698 > > Though I have no explanation as to why kudu would not be able to make local > connections within my machine. (fedora 29, OpenSSL 1.1.1b FIPS 26 Feb 2019) > I attached the full test report. Can someone help me figure out how to > further debug this, or is there any additional information I can provide? > > Best Regards > Clemens Valiente
