Caideyipi opened a new pull request, #18887:
URL: https://github.com/apache/iotdb/pull/18887

   ## Description
   
   `IoTDBSessionRelationalIT.tearDown()` can fail with status 304 when an 
asynchronous `DROP TABLE` procedure is still finishing as cleanup drops its 
database. For example, `insertAllNullSqlTest` drops `db1.all_null` immediately 
before database cleanup.
   
   Retry each database drop for up to 60 seconds when the server returns 
`OVERLAP_WITH_EXISTING_TASK`, using the existing table session and Awaitility 
on the same thread. Other statement errors and connection errors propagate 
immediately.
   
   ## Validation
   
   - Integration-test compilation, Checkstyle, and Spotless passed.
   - Focused `TableSimpleIT` run of `insertAllNullSqlTest`, 
`dropTableOfTheSameNameTest`, and `deleteTableAndWriteDifferentTypeTest`: 3 
tests passed; Failsafe verification passed.
   - Local fault injection against the actual `tearDown()` method: normal 
cleanup and repeated 304 responses on all three databases completed 
successfully; unexpected statement errors and connection errors propagated 
immediately, with the session closed in every case.
   - Full `IoTDBSessionRelationalIT` run with the locally installed runtime: 28 
of 29 tests passed, with no cleanup errors. `insertWrongTimeSqlTest` expected 
`701: Unsupported expression: (1 + 1)` but received `507: No Field column 
present, please check the request`. Compiling the unchanged `origin/master` 
test into a separate directory and running that method against the same runtime 
reproduced the identical assertion failure.
   
   - [x] Self-reviewed.
   - [x] Tested in a 1 ConfigNode / 1 DataNode cluster.
   


-- 
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: [email protected]

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

Reply via email to