I know that we have never set the schedule parameter to 1 millisecond. We
have specified either 100 or 1000. I wondered why it was writing so
frequently. I suspect a bug somewhere
However, we will have multiple collections using cdcr, and in some cases
the source collection will have multiple targ
On 12/22/2016 8:10 AM, Webster Homer wrote:
> While testing CDCR I found that it is writing tons of log messages per
> second. Example:
> 2016-12-21 23:24:41.652 INFO (qtp110456297-13) [c:sial-catalog-material
> s:shard1 r:core_node1 x:sial-catalog-material_shard1_replica1]
> o.a.s.c.S.Request [si
On 1/6/2017 8:21 AM, Webster Homer wrote:
> I figured our problem with the filesystem, by default the root logger
> is configured with the CONSOLE logger, which is NOT rotated and
> eventually filled up the file system. That doesn't exonerate the CDCR
> logging problem though. The thing writes a hu
I figured our problem with the filesystem, by default the root logger is
configured with the CONSOLE logger, which is NOT rotated and eventually
filled up the file system. That doesn't exonerate the CDCR logging problem
though. The thing writes a huge amount of junk to the logs, information
that lo
On 1/3/2017 1:12 PM, Webster Homer wrote:
> We use the default log4j.properties file which rolls the log file to
> solr.log.1, solr.log.2 ... which isn't really the problem. What is
> also happening is that solr.log.1 gets renamed to
> solr_log_20170103_1110 with a timestamp as the file name. How d
So since the logging messages are not from an actual class, how do I
suppress the CDCR INFO messages? I really do want normal INFO messages but
they get swamped by CDCR.
Even when CDCR issues a WARN message, it issues thousands of them.
We use the default log4j.properties file which rolls the log
It’s org.apache.solr.core.SolrCore.Request - not an actual class.
Alan Woodward
www.flax.co.uk
> On 3 Jan 2017, at 16:08, Webster Homer wrote:
>
> I am working on changing the log rotation, but looking at the message:
>
> 2016-12-21 23:24:41.653 INFO (qtp110456297-18) [c:sial-catalog-materia
I am working on changing the log rotation, but looking at the message:
2016-12-21 23:24:41.653 INFO (qtp110456297-18) [c:sial-catalog-material
s:shard1 r:core_node1 x:sial-catalog-material_shard1_replica1]
o.a.s.c.S.Request [sial-catalog-material_shard1_replica1] webapp=/solr
path=/cdcr params={
Seems like a bandaid would be to insure your Solr logs rotate
appropriately quickly.
That doesn't address the CDCR loging verbosity, but it might get you by.
You can also change the logging at the class level by appropriately editing the
log4j properties file. Again perhaps not the best solution
The logs filled up the file system and caused CDCR to fail due to a
corrupted Tlog file.
On Thu, Dec 22, 2016 at 9:10 AM, Webster Homer
wrote:
> While testing CDCR I found that it is writing tons of log messages per
> second. Example:
> 2016-12-21 23:24:41.652 INFO (qtp110456297-13) [c:sial-cat
While testing CDCR I found that it is writing tons of log messages per
second. Example:
2016-12-21 23:24:41.652 INFO (qtp110456297-13) [c:sial-catalog-material
s:shard1 r:core_node1 x:sial-catalog-material_shard1_replica1]
o.a.s.c.S.Request [sial-catalog-material_shard1_replica1] webapp=/solr
pat
11 matches
Mail list logo
