-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Jeff,
On 9/26/18 11:35, Jeff Courtade wrote: > My concern with using g1 is solely based on finding this. Does > anyone have any information on this? > > https://wiki.apache.org/lucene-java/JavaBugs#Oracle_Java_.2F_Sun_Java_ .2F_OpenJDK_Bugs > > "Do not, under any circumstances, run Lucene with the G1 garbage > collector. Lucene's test suite fails with the G1 garbage collector > on a regular basis, including bugs that cause index corruption. > There is no person on this planet that seems to understand such > bugs (see https://bugs.openjdk.java.net/browse/JDK-8038348, open > for over a year), so don't count on the situation changing soon. > This information is not out of date, and don't think that the next > oracle java release will fix the situation." That language is 3 years old and likely just hasn't been updated after it was no longer relevant. Also, it isn't attributed to anyone in particular (it's anonymous), so ... maybe it was one person's opinion and not a project-initiated warning. - -chris > On Wed, Sep 26, 2018 at 11:08 AM Walter Underwood > <wun...@wunderwood.org> wrote: > >> We’ve been running G1 in prod for at least 18 months. Our biggest >> cluster is 48 machines, each with 36 CPUs, running 6.6.2. We also >> run it on our 4.10.4 master/slave cluster. >> >> wunder Walter Underwood wun...@wunderwood.org >> http://observer.wunderwood.org/ (my blog) >> >>> On Sep 26, 2018, at 7:37 AM, Jeff Courtade >>> <courtadej...@gmail.com> >> wrote: >>> >>> Thanks for that... I am just starting to look at this I was >>> unaware of the license debacle. >>> >>> Automated testing up to 10 is great. >>> >>> I am still curious about the GC1 being supported now... >>> >>> On Wed, Sep 26, 2018 at 10:25 AM Zisis T. <zist...@runbox.com> >>> wrote: >>> >>>> Jeff Courtade wrote >>>>> Can we use GC1 garbage collection yet or do we still need >>>>> to use CMS? >>>> >>>> I believe you should be safe to go with G1. We've applied it >>>> in in a >> Solr >>>> 6.6 cluster with 10 shards, 3 replicas per shard and an index >>>> of about 500GB (1,5T counting all replicas) and it works >>>> extremely well (throughput > 99%). The use-case includes >>>> complex search queries and faceting. There is also this post >>>> you can use as a starting point >>>> >>>> >> http://blog.cloudera.com/blog/2017/06/apache-solr-memory-tuning-for-p roduction/ >>>> >>>> >>>> >>>> >>>> >> - -- >>>> Sent from: >>>> http://lucene.472066.n3.nabble.com/Solr-User-f472068.html >>>> >>> -- >>> >>> Jeff Courtade M: 240.507.6116 <(240)%20507-6116> >> >> -- > > Jeff Courtade M: 240.507.6116 > -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlur5i0ACgkQHPApP6U8 pFioLw/9HzPmNo1wtsfZDIsJjXy4i+F0YYqBFKRqXcPH8mLgpxicE5enRVI9he6p 1Z3Mz0wzFj/H91eWktmGyNSKSmFjkYI2IgCBrsZv1gPDFn3mI3TwapJgTR0J4GAg wXB/9GRHuCCTz7qvfQexBOwOt25OKVOhcvNFVI8bxV0hFl58Nlo56Qzt33X/JS32 jH2jIlz77pal1t5ZhnXJwCSWQyWsLnr5GtoxDisvvOl1o3Ey/WIllvCe8x7M+PvA 0/DIK/5niTSCwcv0LVCPIWsE/HCjsSWfdhnhtTnu1088OTKwb2dsa7wyBJItZUzw fCTcmcGclViGUa2QAnXNFiVPj1y0PhFxAPMCU6mWPerCSH6cYn5neicsp2AYovoj dRcs4LGrGf0S7PVJBq/DQdb44XbzvFkkp2SjS9WAnLpBv7RwP4bWfDvMCJsZWJOU 8J2r4ZbkVUjByQ3mAXMZN7bKC6hHBQLLzAwodloAV0OWHJ+Io96flTclDRPt4N6e J8olEQezDKcgkZDg0GV8I9WxUzeTHI+QvnZxUzwsT/sJUPgxjSDjHlous5HU29ay 6lynoEjVFJd4yYAwh6gaRPMw34xKFT6a62D6bDmcL0MqPCpbcbOny+kgx0k7bzl5 FNsapJ5vCIaG0/tPTuWEY/jaqmhNNznXDr+sEX5l8Sk1ZQz8+/U= =Y8qg -----END PGP SIGNATURE-----
