You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Ishan Chattopadhyaya (JIRA)" <ji...@apache.org> on 2019/06/11 09:03:00 UTC
[jira] [Assigned] (SOLR-13535) Segment missing from running Solr
node in GCP
[ https://issues.apache.org/jira/browse/SOLR-13535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ishan Chattopadhyaya reassigned SOLR-13535:
-------------------------------------------
Assignee: Ishan Chattopadhyaya
> Segment missing from running Solr node in GCP
> ---------------------------------------------
>
> Key: SOLR-13535
> URL: https://issues.apache.org/jira/browse/SOLR-13535
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Environment:
>
> Reporter: navneet mathpa
> Assignee: Ishan Chattopadhyaya
> Priority: Minor
> Labels: google-cloud-storage, solr
>
> Hello,
> We found a weird bug where segment were automatically deleted / missing inside the running Solr node in google cloud . When I found the issue I thought I could be because of the older version (4.10) that we are using but [~ichattopadhyaya] also encountered with this issue recently in GCP .
> After that Solr goes to recovery.
> I do not have logs or screenshot with me as of now to put here , as I found this issue a long back and ignored thinking it could be because of the older Solr version with default garbage collector.
> Is there any bug Solr running with GCP ?
>
>
> Thanks,
> Navneet
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org