title: Max frame length of 65536 has been exceeded
body: <p>I have a set up where I am using the gremlin-core library to query a remote Janusgraph server. The data size is moderate for now but will increase in the future.</p>
  
  <p>A few days ago, I saw the "Max frame length of 65536 has been exceeded" error on my client. The value for the maxContentLength parameter in my server yaml file was set to default (65536). I dug up the code and realized that I am sending a large array of vertex ids as a query parameter to fetch vertices. I applied a batch to the array with a size of 100 vertex ids per batch and it resolved the issue.</p>
  
  <p>After sometime I started seeing this error again in my client logs. This time around, there was no query with a large number of parameters being sent to the server. I saw a proposed solution on this topic which said that I need to set the maxContentLength parameter on the client-side as well. I did that and the issue got resolved. However, it raised a few questions regarding the configuration parameters, their values and their impact on the query request/response size.</p>
  
  <ol>
  <li>Is the maxContentLength parameter related to the response size of a query? If yes, how do I figure out the value for this parameter with respect to my database size?</li>
  <li>Are there any other parameters that dictate the maximum size of the query parameters in the request? If yes, which are they and how do they relate to the size of the query parameters?</li>
  <li>Are there any parameters that dictate the size of a query response?  If yes, which are they and how do they relate to the size of the query response?</li>
  </ol>
  
  <p>The answers to these questions are crucial for me to make a robust server that will not break under the onslaught of data.</p>
  
  <p>Thanks in advance</p>
  
  <p>Anya</p>