[
https://issues.apache.org/jira/browse/SOLR-12436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16521556#comment-16521556
]
Shawn Heisey commented on SOLR-12436:
-------------------------------------
bq. Have working but 15 minuts to work
In this respect, the .system collection is like any other Solr index. If it
takes 15 minutes for a change to the index to become visible, that sounds like
there's an issue with commits -- in that the commit is not happening right away
and it gets triggered in some other way 15 minutes later.
I've just located and looked at the solrconfig.xml file that gets used by the
.system collection in the master branch, and I have the following things to say
about it:
* autoCommit has openSearcher set to true, but the config is
<maxDocs>1</maxDocs>
** deletes probably do not count towards maxDocs.
** I'm really wondering what is resulting in the commit 15 minutes later,
because I do not see anything in the config that would cause it.
** IMHO, the autoCommit should use maxTime of 1000 instead of maxDocs. I
would not normally advocate such a short maxTime, but the config has no caches,
so commits should be really fast.
* The max blob size in the config defaults to 5 MB. There are contrib jars
included with Solr that are larger than this. The size is configurable with a
system property, but I think the default should accommodate any jar that Solr
comes with and most jars a user would add, so I'd set it to 20MB.
* I think I've seen mention of warning messages resulting from the use of
LATEST in luceneMatchVersion. Using LATEST does mean that we don't have to
update it with each release, but users might get worried about seeing the
resulting log message. I personally would rather list a specific version, even
if updating it does get missed on a release. I doubt that having an old
version there would matter much.
* I don't think the updateLog directory should be configurable with a system
property. It should use the default. I think it's somewhat dangerous to have
this configurable in ANY core, but for this particular one, it should
definitely not be something the user can influence.
* If StandardDirectoryFactory uses mmap, then I have nothing to say about
that. If it doesn't, then I would probably use MMapDirectoryFactory. There's
definitely no reason to use the NRT factory.
This is the solrconfig.xml file in master for the .system collection:
{code:xml}
<?xml version="1.0" ?>
<config>
<luceneMatchVersion>LATEST</luceneMatchVersion>
<directoryFactory name="DirectoryFactory"
class="${solr.directoryFactory:solr.StandardDirectoryFactory}"/>
<updateHandler class="solr.DirectUpdateHandler2">
<updateLog>
<str name="dir">${solr.ulog.dir:}</str>
</updateLog>
<autoCommit>
<maxDocs>1</maxDocs>
<openSearcher>true</openSearcher>
</autoCommit></updateHandler>
<requestHandler name="/select" class="solr.SearchHandler" default="true" />
<requestHandler name="/blob" class="solr.BlobHandler">
<lst name="invariants">
<str name="maxSize">${blob.max.size.mb:5}</str>
</lst>
</requestHandler>
</config>
{code}
> Can"t delete BLOB element in SolrCloud
> --------------------------------------
>
> Key: SOLR-12436
> URL: https://issues.apache.org/jira/browse/SOLR-12436
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Environment: Debian
> SolrCloud 6 and 7
> Reporter: Maxence SAUNIER
> Priority: Major
>
> Hello,
> The documentation said on the BLOB API page:
> "Deletes can be performed with standard REST delete commands."
> So, I have test to delete a blob file version but thise commands do not
> working:
> {code}
> curl -X "DELETE"
> http://srv-formation-solr3:8983/solr/.system/blob/CityaUpdateProcessorJar/14
> {code}
> This command return just the file informations:
> {code}
> {
> "responseHeader":{
> "zkConnected":true,
> "status":0,
> "QTime":1},
> "response":{"numFound":1,"start":0,"docs":[
> {
> "id":"CityaUpdateProcessorJar/14",
> "md5":"45aeda5a01607fb668cec26a45cac9e6",
> "blobName":"CityaUpdateProcessorJar",
> "version":14,
> "timestamp":"2018-05-30T12:59:40.419Z",
> "size":22483}]
> }}
> {code}
> So, I have test to delete directly on the Solr interface with the query page
> XML:
> {code}
> <delete><query>id:CityaUpdateProcessorJar/14</query></delete>
> {code}
> And not working.
> Thanks for your help,
> Maxence
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
