You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by "jnturton (via GitHub)" <gi...@apache.org> on 2023/02/09 12:12:32 UTC

[GitHub] [drill] jnturton commented on pull request #2752: DRILL-8397: Drill prints warnings to console when starting it

jnturton commented on PR #2752:
URL: https://github.com/apache/drill/pull/2752#issuecomment-1424093562

   Regarding the sporadic failures of the unit test testBasicCTASWithScalarDataTypes that have been showing in recent CI runs, and now also here, it looks to me like [the Thread.sleep(15_000) that it uses](https://github.com/jnturton/drill/blob/83bf04cd815e6c6d22d9ef04550cd8113bd9f905/contrib/storage-splunk/src/test/java/org/apache/drill/exec/store/splunk/SplunkWriterTest.java#L113) to wait for an INSERT to go through is not always enough to ensure that Splunk will return the record needed for the subsequent schema validation to pass.
   
   Locally I've been able to reproduce both successes and failures of this test with a range of sleep durations from 6_000 to 60_000 so I'm not sure if there is a magic number here, or what it might be. Stepping back further, I don't know if Splunk ever takes a transactional approach to loading data - maybe it makes no guarantees beyond "Thanks, I'll index this later"?
   
   CC @cgivre.
   


-- 
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.

To unsubscribe, e-mail: dev-unsubscribe@drill.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org