[ 
https://issues.apache.org/jira/browse/LUCENE-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401027#comment-17401027
 ] 

Rayane commented on LUCENE-10053:
---------------------------------

[~dweiss] Thanks for your help !

I tried creating a dump file from Task Manager on the Elastic process which was 
stuck, but it didn't seem to work.

I'm not a Java expert actually, how could I get a proper dump when this is 
happening ? 

 

> Lucene file deletion seems to hang on Windows Server
> ----------------------------------------------------
>
>                 Key: LUCENE-10053
>                 URL: https://issues.apache.org/jira/browse/LUCENE-10053
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/other
>    Affects Versions: 8.3
>         Environment: Windows Server 2019 16Go RAM 8vCPU
>            Reporter: Rayane
>            Priority: Critical
>              Labels: elasticsearch, refresh
>
> Hi everyone,
>  
> Firstly, i would like to apologize if it's not the right spot to post my 
> issue, but it's been month me and my team are stuck on this.
> We're using an ElasticSearch cluster for months now. Sometimes, a nodes is 
> just getting stuck for a unknown reason.
> When i'm trying to check threads contention, i'm getting this stackTrace : 
>  
> [Elastic_hot threads|https://pastebin.com/g4mPD0xA]
> It seems that the inner file deletion is getting stuck by something .. In my 
> opinion, a deletion is an atomic operation so i can't figured it out how it 
> can hangs forever. I need to restart ElasticSearch to have my node back (i 
> have to kill the process actually). I disabled Antivirus and backup process 
> on these servers and still getting these errors randomly 2 or 3 times per 
> month.
> Do you have any clue on what i should care about ?
>  
> Thank you for your help



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to