Did I reach the character limit of :set in Skytable?

Third Party Coronium
#1

Hi, I’m trying to connect my game to an Amazon EC2 instance with Skytable hosted.

While everything else seems to work, I am unable to set any data bigger than ~8300 characters.

I got the following message in the ‘event.error’ property: “500: Internal error”. Thus an error occurs in the server itself. I went looking for the log files:

The redis.log seems alright, but the nginx.log has this odd error message whenever I try to set data > 8300 characters:

2017/08/07 12:52:36 [warn] 3553#0: *65 a client request body is buffered to a temporary file /usr/local/coronium/nginx/client_body_temp/0000000033, client: 81.206.196.96, server: localhost.domain, request: “POST / HTTP/1.1”, host: “52.30.111.239:7173”

2017/08/07 12:52:36 [error] 3553#0: *65 lua entry thread aborted: runtime error: [string “coronium.app”]:0: attempt to index a nil value

stack traceback:

coroutine 0:

[string “coronium.app”]: in function <[string “coronium.app”]:0>

[string “coronium.input”]: in function ‘request’

content_by_lua(coronium.server.conf:29):2: in function <content_by_lua(coronium.server.conf:29):1>, client: 81.206.196.96, server: localhost.domain, request: “POST / HTTP/1.1”, host: “52.30.111.239:7173"”

Is anyone familiar with this problem, or knows how to solve it?

#2

Apparently the default configuration of nginx does not allow requests above a certain size to optimize performance…

I have added the following lines to the /usr/local/coronium/conf/nginx.conf:

client\_body\_buffer\_size 10M; client\_max\_body\_size 10M;

Which fixed my problem :slight_smile: The 10M sets the limit to 10MB, but you can change that to any other value

#3

Hi,

My apologies for not seeing this sooner, and great job on resolving the issue.

My only suggestion is to use the lowest setting that you think you will need as this setting is per request. At a high request rate, this could cause issues with memory and end up slowing down your system. Of course that’s not an issue with a high memory setup.

I’ll go ahead and hard code a value in the config as well, probably around 512k, which should be more than enough in most use cases. Thank you for sharing your answer.

-dev

#4

Apparently the default configuration of nginx does not allow requests above a certain size to optimize performance…

I have added the following lines to the /usr/local/coronium/conf/nginx.conf:

client\_body\_buffer\_size 10M; client\_max\_body\_size 10M;

Which fixed my problem :slight_smile: The 10M sets the limit to 10MB, but you can change that to any other value

#5

Hi,

My apologies for not seeing this sooner, and great job on resolving the issue.

My only suggestion is to use the lowest setting that you think you will need as this setting is per request. At a high request rate, this could cause issues with memory and end up slowing down your system. Of course that’s not an issue with a high memory setup.

I’ll go ahead and hard code a value in the config as well, probably around 512k, which should be more than enough in most use cases. Thank you for sharing your answer.

-dev