Possible bug in AWS environment about connect-memcached HOT 10 CLOSED

I decided to move to the https://github.com/liamdon/connect-memjs

from connect-memcached.

Hi there!
@archasek Could you post some more info about the memcached configuration? Are you using Memcached bundled with MySQL RDS or ElastiCache?

from connect-memcached.

@balor hi :)
Memcached bundled with MySQL RDS at the moment

from connect-memcached.

To be honest I didn't used this RDS configuration, could you post the memcached settings?

from connect-memcached.

Here you go:

STAT maxbytes 67108864
STAT maxconns 1024
STAT tcpport 11211
STAT udpport 11211
STAT inter NULL
STAT verbosity 1
STAT oldest 0
STAT evictions on
STAT domain_socket NULL
STAT umask 700
STAT growth_factor 1.25
STAT chunk_size 48
STAT num_threads 4
STAT num_threads_per_udp 0
STAT stat_key_prefix :
STAT detail_enabled no
STAT allow_detailed yes
STAT reqs_per_event 20
STAT reqs_per_tap_event 50
STAT cas_enabled yes
STAT tcp_backlog 1024
STAT binding_protocol auto-negotiate
STAT auth_enabled_sasl no
STAT auth_sasl_engine none
STAT auth_required_sasl no
STAT item_size_max 1048576
STAT topkeys 0
STAT logger standard error
END

item_size_max 1048576 something with this setting?

from connect-memcached.

The item_size_max 1048576 means that you can store max 1MB of session store (encrypted), which is the default option for memcached and shouldn't be a problem itself. Do the use of memjs solved the case?

from connect-memcached.

@archasek The encrypted object has been truncated. Can you confirm the contents on save?

from connect-memcached.

@jas-, thanks for asking, but it's been like 2.5 years since I asked my question - I have no chance to confirm this :-). Cheers

from connect-memcached.

@archasek ok, sorry I am just now seeing this. I thought I was watching this repo in order to help @balor support the functionality

from connect-memcached.

Due to insufficient debug data I'm closing this issue.

from connect-memcached.