-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Wei,
On 11/28/18 20:22, Wei wrote: > Hi, > > I use the following http request to start solr index optimization: > > http://localhost:8983/solr/<core>/update?skipError=true -F > stream.body=' <optimize />' > > > The request returns status code 200 shortly, but when looking at > the solr instance I noticed that actual optimization has not > completed yet as there are more than 1 segments. Is the optimize > command async? What is the best approach to validate that optimize > is truly completed? Try this instead: http://localhost:8983/solr/<core>/update?optimize=true&wait=true This will wait until the operation has completed. Note that your client (e.g. curl) may time-out after some time, so you'll want to adjust that timeout to make sure the client doesn't give-up before the optimization operation has completed. As others have said, perhaps you don't actually need to optimize anythin g. - -chris -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlv//R4ACgkQHPApP6U8 pFi3+w/8C+pvp/XBqHUPeVCd7rEvU1v7mPOx+9lQ/zmU/OE3Y7rmAmVBXiiFvXeT p2tKwhaNSrpx+MoGtaLu0GKg+nczD6K7yxOuRiltmr2KCg+6vCexJAd4yHFIt3H6 FmBnS3Couja7DwD/49pk75o/IkgXj3zok49fbt75AObttQOwXYo06yuijqN/08Wt ieKo/4iLYLwGd3Pii8DnBTu3+IXlQG2eBbdOsNBazr2az0UrOkO+Xuj+IKv8brYr LwMJ36e+m+Q2Gj8ZUvTQ8lTQNs7HD5giqtQXMelUXF7dcGPSwG9jCMvSTHfb+0rs woMIt6ehRsW2CeP2Vrm2qY5gxeVIK5LwkwRcjZUq4gIDes3eiOImDLCE8Fhxxn2Z xifKL7fQPlwdQWWXm2KDfTN+VvLVyWeA1n5z7drgD13VARdbA5c66iaIgguw0uKP an3YC8uYbcZJolyWt/yu9r01pBTUsnxCpXDo5s5xUAz0LWdoRSNRDS872ohZxRIR mcfCPbYUwNyhnclvzIPPcE8Z2sbCNaHcc2b5ZuavlA4PgEwFxgI1PweDXSa2Tuxg lzuus5uS/U8lGSrkheeQDBmX6nCl2n1jsnXS4CXLGNHzH3uOVkJFmFraVNZCav16 t7SKTQc8Yc9P3AbdesG13C0iQDGjo3WLoKg7ghO3khoEL+NMKbQ= =1wy3 -----END PGP SIGNATURE-----
