How about using "logstash" for this? I know its ES and not solr, but it is
a free tool that is out there and no need to re-invent the wheel
On Jun 5, 2016 9:09 AM, "Anil" wrote:
> Hi ,
>
> i would like to index logs using to enable search on it in our application.
>
> The problem would be index a
t this
> new replica and the leader with &distrib=false), use
>DELETEREPLICA on the "bad" core.
>
> Best,
> Erick
>
> On Wed, Jun 1, 2016 at 5:54 AM, Ilan Schwarts wrote:
> > Hi,
> > We have in lab SolrCloud 5.2.1
> > 2 Shards, each shar
; than once too.
>
> Best,
> Erick
>
> On Wed, Jun 1, 2016 at 9:26 AM, Ilan Schwarts wrote:
> > Since its working in non ssl, i dont think its commit issue, it is the
> same
> > pc, i just update scheme on zoomeeper to https and un-comment the ssl
> > settings
Since its working in non ssl, i dont think its commit issue, it is the same
pc, i just update scheme on zoomeeper to https and un-comment the ssl
settings on solr.in.cmd.
On Jun 1, 2016 7:25 PM, "Ilan Schwarts" wrote:
> If a document was added on both cores/nodes. Doesnt it mean
If a document was added on both cores/nodes. Doesnt it mean the document
was successfully added and commited?
On Jun 1, 2016 7:23 PM, "Erick Erickson" wrote:
> Did you issue a commit?
>
> Best,
> Erick
>
> On Wed, Jun 1, 2016 at 8:15 AM, Ilan Schwarts wrote:
&g
dding the document, it is added
to the collection, but the last modified is not updated.
Is this a bug ? known issue ?
Update:
After restarting all the cores, the value of Last Modified is valid, But it
happens only after restart and not after update ot collection/index document
Than
dding the document, it is added
to the collection, but the last modified is not updated.
Is this a bug ? known issue ?
Thanks
--
-
Ilan Schwarts
reproduce.
Is it possible to merge the 2 cores into 1, and then split that core to 2
cores ?
Or maybe to enforce sync if possible ?
The other shard, Shard 2 is functioning well, the replication works fine,
when adding a document to 1 core, it will replicate it to the other.
--
-
Ilan Schwarts
10.132.2.110
What did i define wrong ?
--
-
Ilan Schwarts
ne.
> > Since it seems the indexing process is CPU bound I was wondering whether
> > 32 logical cores with twice indexing threads will perform better.
> > Thanks,
> > Avner
> >
> > -Original Message-
> > From: Ilan Schwarts [mailto:ila...@gmail.com]
Rowe" wrote:
> Hmm, not sure what’s happening. Have you tried converting the backslashes
> in your paths to forward slashes?
>
> --
> Steve
> www.lucidworks.com
>
> > On Mar 8, 2016, at 3:39 PM, Ilan Schwarts wrote:
> >
> > Hi, thanks for reply.
> &
What is the solr version and shard config? Standalone? Multiple cores?
Spread over RAID ?
On Mar 9, 2016 9:00 AM, "Avner Levy" wrote:
> I have a machine with 16 real cores (32 with HT enabled).
> I'm running on it a Solr server and trying to reach maximum performance
> for indexing and queries (i
:
> Hi Ilan,
>
> Looks like you’re modifying solr.in.sh instead of solr.in.cmd?
>
> FYI running under Cygwin is not supported.
>
> --
> Steve
> www.lucidworks.com
>
> > On Mar 8, 2016, at 11:51 AM, Ilan Schwarts wrote:
> >
> > Hi all, I am trying
i replace
SOLR_SSL_KEY_STORE=C:\solr-5.2.1\server\etc\solr-ssl.keystore.jks with
SOLR_SSL_KEY_STORE=NOTHING_REALISTIC
it will write the same error, i suspect i dont deliver the path as it
should be.
Any suggestions ?
Thanks
--
-
Ilan Schwarts
/display/solr/UpdateHandlers+in+SolrConfig
They tell you
${solr.ulog.dir:}
500
20
65536
So what should I use ? solr.data.dir Or solr.udir.dir ? Or both nodes ?
I am trying to integrate my existing UpdateRequestHandler plugin.
--
-
Ilan Schwarts
my typo, I have added DistributedUpdateProcessorFactory before
solr.RunUpdateProcessorFactory and not solr.RunUpdateProcessorFactory..
Then i received exception stating wrote there are 2 declared
solr.DistributedUpdateProcessorFactory
On Sun, Feb 21, 2016 at 11:01 PM, Ilan Schwarts wrote:
>
lr cloud with old-style replication is tricky, so please explain what the
> reasoning is...
>
> Best
> Erick
> On Feb 21, 2016 21:24, "Ilan Schwarts" wrote:
>
> > Hi, we had a running solr 4.3.1 with 1 core and no replication.
> > We are migrating to
;node_name":"10.171.3.106:8985_solr",
"state":"active",
"router":{"name":"compositeId"},
"maxShardsPerNode":"1",
"autoAddReplicas":"false"}}
What is weird, if i stop all solr cores, and then start, it will be synced,
the documents will be on both nodes.
I am using a custom update handler, maybe the problem is there ? i have set
it as before:
*Custom update handler:*
WitStandardUpdater
url
batchStatus
0
1
true
host
port
queryId
--
-
Ilan Schwarts
18 matches
Mail list logo
