You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@solr.apache.org by "Haythem Khiri (Jira)" <ji...@apache.org> on 2022/12/08 23:12:00 UTC

[jira] [Updated] (SOLR-16577) Core load issues are not always logged

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

Haythem Khiri updated SOLR-16577:
---------------------------------
    Description: It's possible for a core load failure to not have its cause logged. At least the failure is tracked in a metric and one can do an admin request to fetch the cau (requires SSH access in prod) but really it ought to be logged so one can more easily see what the problem is.  (was: It's possible for a core load failure to not have its cause logged. At least the failure is tracked in a metric and one can do an admin request to fetch the cause (requires SSH access in prod) but really it ought to be logged so one can more easily see what the problem is.)

> Core load issues are not always logged
> --------------------------------------
>
>                 Key: SOLR-16577
>                 URL: https://issues.apache.org/jira/browse/SOLR-16577
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Haythem Khiri
>            Priority: Minor
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> It's possible for a core load failure to not have its cause logged. At least the failure is tracked in a metric and one can do an admin request to fetch the cau (requires SSH access in prod) but really it ought to be logged so one can more easily see what the problem is.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org