Closing, Reopening Warning

[rohantandon96]

Hi,

• I am using "io.monix" %% "shade" % "1.10.0" in build.sbt and receiving following warning message:

Closing, and reopening {QA sa=memcachedOnAWS, #Rops=0, #Wops=1, #iq=2, topRop=null, topWop=Cmd: 1 Opaque: 59 Key: myKey Cas: 0 Exp: 0 Flags: 0 Data Length: 12406131, toWrite=0, interested=4}, attempt 0.

• The the size of the data I am trying to insert is ~12MB (Data Length: 12406131 in bytes) and I have increased the memcached maxValue size to accommodate for this, however still receive the above warning.

• As a result of the warning, the value is never inserted into memcached.

• Similar issue was resolved here: Nullpointer while inserting cache values above 6mb memcached/memcached#333 but increasing maxSize is not working for me.

• In terms of stack trace, I get a NPE at same line as above issue

Can you please help.

[lloydmeta]

If this is configurable on the underlying Spymemcached client (I haven't checked), it might be worth trying to do it in a similar fashion #54. Do you want to take on this @rohantandon96 ?

[rohantandon96]

sure i will give it a shot @lloydmeta and report back with results. Thanks.

[rohantandon96]

sorry mate @lloydmeta, no luck with adding a timeOut threshold. Get the same error

Closing, and reopening {QA sa=memcachedOnAWS, #Rops=0, #Wops=1, #iq=2, topRop=null, topWop=Cmd: 1 Opaque: 59 Key: myKey Cas: 0 Exp: 0 Flags: 0 Data Length: 12406131, toWrite=0, interested=4}, attempt 0.

Can i provide anything to help debug this issue?

[lloydmeta]

Err, no I think you misunderstood me. I meant trying to do something similar to #54 in terms of trying to add the ability to configure maxValue on the underlying Spymemcached client in a similar way, not try to solve it by configuring timeout :)