redsanket opened a new pull request #23700: [SPARK-25692] Fix 
ChunkFetchIntegrationSuite
URL: https://github.com/apache/spark/pull/23700
 
 
   ## What changes were proposed in this pull request?
   
   How to reproduce
   ./build/mvn test 
-Dtest=org.apache.spark.network.RequestTimeoutIntegrationSuite,org.apache.spark.network.ChunkFetchIntegrationSuite
 -DwildcardSuites=None test
   furtherRequestsDelay Test within RequestTimeoutIntegrationSuite was holding 
onto worker references. The test does close the server context but since the 
threads are global and there is sleep of 60 secs to fetch a specific chunk 
within this test, it grabs on it and waits for the client to consume but 
however the test is testing for a request timeout and it times out after 10 
secs, so the workers are just waiting there for the buffer to be consumed by 
client as per my understanding. 
   
   This tends to happen if you dont have enough IO threads available on the 
specific system and also the order of the tests being run determines its 
flakyness like if ChunkFetchIntegrationSuite runs first then there is no issue. 
For example on mac with 8 threads these tests run fine but on my vm with 4 
threads it fails. It matches the number of fetch calls in 
RequestTimeoutIntegrationSuite.
   
   So do we really need it to be static?
   
   I dont think this requires a global declaration as these threads are only 
required on the shuffle server end and on the client TransportContext 
initialization i.e the Client don't initialize these threads. The Shuffle 
Server initializes one TransportContext object. So, I think this is fine to be 
an instance variable and I see no harm.
   
   ## How was this patch tested?
   I did some manual tests and it looks good
   Please review http://spark.apache.org/contributing.html before opening a 
pull request.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to