Details
-
Task
-
Status: Closed
-
Resolution: Done
-
None
-
None
-
None
Description
Here are the stacks when test/format hangs. Mentioned in WT-748.
8 at,__wt_cond_wait,__wt_cache_full_check,__wt_page_in_func,__wt_page_swap_func,__wt_col_search,__wt_btcur_update,__curfile_update,col_update,ops,start_thread,clone
|
3 at,__wt_cond_wait,__wt_cache_full_check,__wt_page_in_func,__wt_page_swap_func,__wt_col_search,__wt_btcur_search,__curfile_search,read_row,ops,start_thread,clone
|
3 at,__wt_cond_wait,__wt_cache_full_check,__cursor_leave,__cursor_func_init,__wt_btcur_update,__curfile_update,col_update,ops,start_thread,clone
|
2 at,__wt_cond_wait,__wt_cache_full_check,__session_begin_transaction,ops,start_thread,clone
|
2 at,__wt_cond_wait,__wt_cache_full_check,__cursor_leave,__cursor_func_init,__wt_btcur_insert,__curfile_insert,col_insert,ops,start_thread,clone
|
2
|
1 nanosleep,usleep,wts_ops,main
|
1 at,__wt_cond_wait,__wt_cache_evict_server,start_thread,clone
|
michaelcahill I have started another run on the AWS HD system that has eviction verbose turned on. A script of the verbose output can be found in /mnt/fast/sue/script.748. The home directory is ~sue/wt.dev/build_posix/test/format/RUNDIR. I believe when it hangs, information will still be written to the script each time eviction runs but does not find anything. Probably looking at the dates on the files in RUNDIR compared to the current time is the easiest way to know if it is hung.