[jira] [Updated] (IGNITE-25494) Add "onSpinWait" to timestamp updater thread

["Ivan Bessonov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-25494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Bessonov updated IGNITE-25494:
-----------------------------------
    Ignite Flags:   (was: Docs Required,Release Notes Required)

> Add "onSpinWait" to timestamp updater thread
> --------------------------------------------
>
>                 Key: IGNITE-25494
>                 URL: https://issues.apache.org/jira/browse/IGNITE-25494
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Ivan Bessonov
>            Assignee: Ivan Bessonov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.1
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Following problem occurred while local testing (with safe-point timeout being 1 second):
> {code:java}
> [118.719s][warning][safepoint] # SafepointSynchronize::begin: Timeout detected:
> [118.719s][warning][safepoint] # SafepointSynchronize::begin: Timed out while spinning to reach a safepoint.
> [118.719s][warning][safepoint] # SafepointSynchronize::begin: Threads which did not reach the safepoint:
> [118.719s][warning][safepoint] # "FastTimestamps updater" #184 daemon prio=5 os_prio=0 cpu=331.99ms elapsed=116.07s tid=0x00007f88a4004370 nid=0x1fb52d sleeping [0x00007f887e9fe000]
> [118.719s][warning][safepoint]    java.lang.Thread.State: TIMED_WAITING (sleeping)
> [118.719s][warning][safepoint] 
> [118.719s][warning][safepoint] # SafepointSynchronize::begin: (End of list) {code}
> Apparently, it can be alleviated with forcing a safe-point into the loop. One way of doing that is using "Thread.onSpinWait()". Let's do it and then see if the problem persists.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)