|
|
Cleanup logs
Updated: 24/06/07 17:43
Created: 23/06/07 21:02
|
|
| The following comment has been added to this issue: |
[ Permlink ] |
|
Author: Georges Racinet
Date: 24/06/07 17:43
Comment:
About the indexing stuff log lines are definitely useful. Please consider that they are till now the only way for people to get a clue about what's wrong with their indexing conf. We need developers, esp 3rd party to be able to do their jobs. Plan for the compass backend:
- remove the input log in ResourceBuilder. It's been mostly useful for me, fetch problems are logged beforehand anyway
- try and control the compass log (that dumps the entire Compass Resource, including fulltext). At least ensure that toString is not called
on the resource if debug log isn't enabled.
|
|
As Bogdan said, there are some performance issues with the logs:
- When indexing a document its content its logged several times (the blob included)
- Also the toString() method of the document - dump the entire document content
- And this method is very used in logs => another performance problem. (dumping the document content each time a log is made
is time consuming and should be avopided)
We also should make sure that when the application is behaving normally, very few and only non-threatening messages appear in the logs when the logger is configured for production (WARNING or INFO levels).
|
|
|
|
![]() |
|
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
