Issue Summary

The error message 'cannot be dropped yet' is used in situations where a dhandle is being closed, not necessarily dropped via WT_SESSION::drop(). This wording is misleading, as the operation may simply be closing the handle, not dropping it.

Context

• The message was originally added because one code path involves WT_SESSION::drop(), but the error can occur in other contexts, such as closing the connection or handle for reasons unrelated to dropping a table.
• The same issue appears in the code at conn_dhandle.c#L394-L396.
• The path to the message includes:

  ___session_drop
  __wt_schema_drop
  __schema_drop
  __drop_file
  __wt_conn_dhandle_close_all
  __conn_dhandle_close_one
  __wt_conn_dhandle_close
  __wt_checkpoint_close
  

• However, the message can also be triggered from other paths that do not involve a drop operation.

Proposed Solution

• Update the error message to use 'closed' instead of 'dropped' to accurately reflect the operation being performed.
• Review all instances where this message appears to ensure it is contextually correct.

Original Slack thread: Slack Thread
This ticket was generated by AI from a Slack thread.