Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-9311

solrcloud so many connections

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Information Provided
    • 4.9
    • None
    • clients - java
    • None

    Description

      firstly, I do not know wether it is a bug or a wrong usage. if this is a wrong usage, I will opligize to disturb you, and tell me what the wrong usage is.

      We are using Solrj 4.9.1 to connect to a Zookeeper. and the solr server version is 4.9.0 We are currently using CloudSolrServer as a singleton to operate index data, and I believe that solrj to zookeeper is a TCP connection, and zookeeper to solrcloud internal is actually a httpconnection.

      we use the zabbix to monitor the solrcloud status, and we deploy solr in Wildfly(JBOSS), for example the http port is 8180, we find the number that connecting with solr on port 8180 is so high. for now we find the number can be around 4000, that is too large.and we find that with the increasing connections, the query speed become slow. the CPU of the solr sever is unstable, and the speed to commit new index data becomes slow as well.

      besides, the JDK version is 1.7.25 to running solr server.

      on the other hand, we have 3 cores with 5 shards, and each shard with one leader and one replication. now the data account goes to be 100 million, and it is still growing up.
      please see the screenshot of Zabbix in the attachments.

      please help me, and looking forward to your reply.

      Thanks.
      Kent

      Attachments

        1. connections.png
          148 kB
          Junfeng Mu
        2. CPU.png
          165 kB
          Junfeng Mu
        3. shards.png
          80 kB
          Junfeng Mu

        Activity

          People

            Unassigned Unassigned
            Kent_Mu Junfeng Mu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: