RUNTIME_ERROR when using GPText
search cancel

RUNTIME_ERROR when using GPText

book

Article ID: 296288

calendar_today

Updated On:

Products

VMware Tanzu Greenplum

Issue/Introduction

While using GPText, the following error is given and the GPText operation fails:
020-11-12 07:31:39.642 ERROR (qtp1531333864-146064) [c:merit.dbo.products s:shard8 r:core_node31 x:merit.dbo.products_shard8_replica_n28] o.a.s.h.RequestHandlerBase org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error from server at http://sdw1.mgmt:18984/solr/merit.dbo.products_shard32_replica_n124: Expected mime type application/octet-stream but got application/json. {
  "error":{
    "metadata":[
      "error-class","org.apache.solr.common.SolrException",
      "root-error-class","org.apache.solr.common.SolrException"],
    "msg":"application/x-www-form-urlencoded content length (5075603 bytes) exceeds upload limit of 4096 KB",
    "code":400}}

It fails when the transfer of data between solr has reached the default limit of 4096 KB (the default number may vary).

Environment

Product Version: 5.7

Resolution

The solution for this is to increase the formdataUploadLimitInKB value. From the above example, we can see that it is looking to transfer 5075 KB or less. You should increase the formdataUploadLimitInKB value to above that value, for example 6000 KB.

You can use gptext-config to update ‘solrconfig.xml’ which belongs to the index you are using. Here is an example:

gptext-config edit -f solrconfig.xml -i {your_index_name}


Then change the value of ‘formdataUploadLimitInKB’, save, and quit.

You can try to increase it more if you still see this issue. The consequence would be that there will have heavy IO transfers in the cluster, please stop data ingesting while you are trying the queries so that Solr nodes do not go down.