You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Varun Thacker (JIRA)" <ji...@apache.org> on 2015/12/10 11:06:11 UTC
[jira] [Commented] (SOLR-8399) New Admin Files UI making extra API
calls
[ https://issues.apache.org/jira/browse/SOLR-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050491#comment-15050491 ]
Varun Thacker commented on SOLR-8399:
-------------------------------------
On a separate note I feel the the CollectionsHandler shouldn't log "Invoked Collection Action..." in info. The very next line has the servlet logging the request . Not worth another Jira though
> New Admin Files UI making extra API calls
> -----------------------------------------
>
> Key: SOLR-8399
> URL: https://issues.apache.org/jira/browse/SOLR-8399
> Project: Solr
> Issue Type: Improvement
> Reporter: Varun Thacker
> Priority: Minor
>
> I was playing around with the new Admin UI and noticed that the Files UI is making extra API calls to Solr .
> Steps to reproduce:
> 1. Go to the Admin UI, select collection, go to the files UI , select a file . So the end URL would be : http://localhost:8983/solr/#/gettingstarted/files?file=solrconfig.xml
> 2. Now click on another file ( say protwords.txt )
> If you look at the logs these are the calls that this one click is making
> {code}
> INFO - 2015-12-10 09:50:46.808; [ ] org.apache.solr.servlet.HttpSolrCall; [admin] webapp=null path=/admin/cores params={indexInfo=false&wt=json&_=1449740448851} status=0 QTime=1
> INFO - 2015-12-10 09:50:46.816; [c:gettingstarted s:shard2 r:core_node4 x:gettingstarted_shard2_replica1] org.apache.solr.core.SolrCore; [gettingstarted_shard2_replica1] webapp=/solr path=/admin/file params={wt=json&_=1449740448963} status=0 QTime=7
> INFO - 2015-12-10 09:50:46.819; [c:gettingstarted s:shard2 r:core_node4 x:gettingstarted_shard2_replica1] org.apache.solr.core.SolrCore; [gettingstarted_shard2_replica1] webapp=/solr path=/admin/file params={file=protwords.txt&contentType=text/plain;charset%3Dutf-8&wt=json&_=1449740448963} status=0 QTime=1
> INFO - 2015-12-10 09:50:46.838; [ ] org.apache.solr.servlet.HttpSolrCall; [admin] webapp=null path=/admin/info/system params={wt=json&_=1449740448854} status=0 QTime=30
> INFO - 2015-12-10 09:50:46.879; [c:gettingstarted s:shard2 r:core_node4 x:gettingstarted_shard2_replica1] org.apache.solr.core.SolrCore; [gettingstarted_shard2_replica1] webapp=/solr path=/admin/file params={file=lang&wt=json&_=1449740448963} status=0 QTime=12
> INFO - 2015-12-10 09:50:46.925; [ ] org.apache.solr.handler.admin.CollectionsHandler; Invoked Collection Action :list with params action=LIST&wt=json&_=1449740448853
> INFO - 2015-12-10 09:50:46.925; [ ] org.apache.solr.servlet.HttpSolrCall; [admin] webapp=null path=/admin/collections params={action=LIST&wt=json&_=1449740448853} status=0 QTime=0
> {code}
> Now the same steps when repeated on the old UI leads to these log lines
> {code}
> INFO - 2015-12-10 09:51:13.623; [c:gettingstarted s:shard1 r:core_node3 x:gettingstarted_shard1_replica1] org.apache.solr.core.SolrCore; [gettingstarted_shard1_replica1] webapp=/solr path=/admin/file params={wt=json&_=1449741073613} status=0 QTime=5
> INFO - 2015-12-10 09:51:13.623; [c:gettingstarted s:shard1 r:core_node3 x:gettingstarted_shard1_replica1] org.apache.solr.core.SolrCore; [gettingstarted_shard1_replica1] webapp=/solr path=/admin/file params={file=protwords.txt&contentType=text/plain;charset%3Dutf-8&_=1449741073616} status=0 QTime=1
> {code}
> So looks like the new admin UI is making addition calls to core admin, collections api and asking for the lang file?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org