lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shalin Shekhar Mangar <shalinman...@gmail.com>
Subject Re: logging in SolrCloud
Date Thu, 04 May 2017 08:48:50 GMT
I'm not a fan of auto-archiving myself and we definitely shouldn't be
doing it before checking if an instance is running. Can you please
open an issue?

On Thu, May 4, 2017 at 12:52 PM, Bernd Fehling
<bernd.fehling@uni-bielefeld.de> wrote:
> Hi Shalin,
>
> sounds like all or nothing method :-)
>
> How about a short check if an instance is still running
> and using that log file before moving it to archived?
>
> Regards
> Bernd
>
> Am 04.05.2017 um 09:07 schrieb Shalin Shekhar Mangar:
>> Yes this is expected. On startup old console logs and gc logs are
>> moved into the archived folder by default. This can be disabled by
>> setting SOLR_LOG_PRESTART_ROTATION=false as a environment variable
>> (search for its usage in bin/solr) but it will also disable all log
>> rotation.
>>
>> On Wed, May 3, 2017 at 5:59 PM, Bernd Fehling
>> <bernd.fehling@uni-bielefeld.de> wrote:
>>> While looking into SolrCloud I noticed that my logging
>>> gets moved to archived dir by starting a new node.
>>>
>>> E.g.:
>>> bin/solr start -cloud -p 8983
>>> -> server/logs/ has solr-8983-console.log
>>>
>>> bin/solr start -cloud -p 7574
>>> -> solr-8983-console.log is moved to server/logs/archived/
>>> -> server/logs/ has solr-7574-console.log
>>>
>>> Is this how it should be or do I have a misconfig?
>>>
>>> Regards
>>> Bernd
>>
>>
>>



-- 
Regards,
Shalin Shekhar Mangar.

Mime
View raw message