epugh commented on PR #1875:
URL: https://github.com/apache/solr/pull/1875#issuecomment-1733907931
i hate having PR's that just hang out open for years in github ;-)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
epugh commented on PR #1875:
URL: https://github.com/apache/solr/pull/1875#issuecomment-1733906940
;-) Okay. That's fair. I'll close this, and if we see value int he future
we can reopen.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
epugh commented on PR #1875:
URL: https://github.com/apache/solr/pull/1875#issuecomment-1733679076
i think we're going to see a lot more change in this area, adding basic
auth, the potential changes aorund ZK.. so thinking this helps build
confidence we didn't break anythingDoes th
epugh commented on PR #1875:
URL: https://github.com/apache/solr/pull/1875#issuecomment-1712485268
@janhoy just to clarify, if I keep the NON zookeeper end 2 end test for
replication, do you see that as valuable and worth merging? I'll split the
zookeeper version of the test out into it's
epugh commented on PR #1875:
URL: https://github.com/apache/solr/pull/1875#issuecomment-1701520212
You are quite right about probably conflating this with my other experiment
to see how it works.if you are running a cluster with six nodes, then you
probably SHOULD be using Solrcloud, an
epugh commented on PR #1875:
URL: https://github.com/apache/solr/pull/1875#issuecomment-170140
> Cool. I don't see the point in testing replication between two isolated
SolrCloud nodes though, is that even supported? Are you thinking about some
kind of usecase where you pull the index f
