[ 
https://issues.apache.org/jira/browse/SOLR-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732712#action_12732712
 ] 

Lance Norskog commented on SOLR-1272:
-------------------------------------

I conflated source code logging and production monitoring logging, which are 
different use cases. The Java Replication code has logging appropriate for a 
code base. Some things are 'info', some are 'warn', and some are 'error'.  

In auto-polling mode, the client does not create a monitoring log. In 
production I would drive the polling from external scripting and maintain my 
own log & error notification (emails/pages to the operator) so that is not 
really a big problem.

My original use case, more clarified, was: if I configure logging to send all 
ReplicationHandler logger calls to a separate file, can I monitor that file as 
a production site operator? Can I use it to debug all problems? Now that I look 
at the logging code & messages I would have to say no. But I have not done this 
experiment.

I predict that "how to monitor & troubleshoot production replication" will 
appear every three days on the solr-user list. I would say close this issue and 
wait.

Lance

> Java Replication does not log actions
> -------------------------------------
>
>                 Key: SOLR-1272
>                 URL: https://issues.apache.org/jira/browse/SOLR-1272
>             Project: Solr
>          Issue Type: Improvement
>          Components: replication (java)
>    Affects Versions: 1.4
>            Reporter: Lance Norskog
>            Assignee: Noble Paul
>             Fix For: 1.4
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Java Replication actions are not logged. There is no trail of full and 
> partial replications.
> All full and partial replications, failed replications, and communication 
> failures should be logged in solr/logs/ the way that the script replication 
> system logs activity.
> This is a basic requirement for production use. If such a log does exist, 
> please document it on the wiki.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to