bigdata4u / spymemcached

Automatically exported from code.google.com/p/spymemcached
0 stars 0 forks source link

Unable to retrieve the file stored to kestrel server #289

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What version of the product are you using? On what operating system?
Spymemcached-2.9.1 on wi

Tell me more...

 While retrieving the file stored into kestrel queue (file is converted to a byte[] and pushed to queue using memcachedclient.java) file is getting corrupted. I noticed the flags of the file while pushing to the queue as 2048 and is zero (0) while getting it from queue. Its happening for normal as well as compressed files.

Thanks
Dharma S

Original issue reported on code.google.com by dso...@gmail.com on 29 Oct 2013 at 3:28

GoogleCodeExporter commented 8 years ago
We don't test against kestrel, and I don't see enough info here to act upon 
this.  If you're saying flags going in are one value and coming out are a 
different value, doesn't that sound like a kestrel bug?

do you have a verbose log demonstrating a problem?

Original comment by ingen...@gmail.com on 7 Nov 2013 at 9:41

GoogleCodeExporter commented 8 years ago
Hi Team,

       As requested attached log file (test_app.log) which holds the information of 1.Pushing a file to queue (test_kestrel_queue) [logs end at line #63]
2.Depth of the queue (test_kestrel_queue) and [logs end at line #73]
3.Popping the actual element that stored from #1. [logs end at line #146]

at line #12 the set command has the flags value set as 2048 and at #109 it 
states the value it received is zero (0).

Please let me know if you are in need of any further info.

Other issue is with the logger, I see there is a mismatch between the actual 
line number that triggered the log statement and the number that got printed to 
log file.
Log File properties:
    log4j.appender.R.layout.ConversionPattern=%d{yyyyMMdd HHmmss,SSS} %p %c.%L - %m%n
and the logger that is assigned to the property "net.spy.log.LoggerImpl" is 
"net.spy.memcached.compat.log.SLF4JLogger.class.getCanonicalName()"

Thanks
Dharma S

Original comment by dso...@gmail.com on 8 Nov 2013 at 6:09

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by ingen...@gmail.com on 8 Nov 2013 at 7:22

GoogleCodeExporter commented 8 years ago
Hi Team,

     May i know if there is any fix available for this?

Thanks
Dharma S

Original comment by dso...@gmail.com on 9 Dec 2013 at 1:01

GoogleCodeExporter commented 8 years ago
Well, looks like kestrel is not storing the flags appropriately? Doesn't look 
like a spy bug here. Can you open a ticket on the kestrel repo and verify the 
behavior with their core team? I've never used kestrel so I won't be much of a 
help there.

Original comment by michael....@gmail.com on 9 Dec 2013 at 1:10

GoogleCodeExporter commented 8 years ago
I verified the same with the ruby client, it was working perfectly (the 
scenario i tested is i pushed an .gz file from the java client using 
spymemcached implementation and retried the item from ruby client (consumed 
message via ruby code). Any ways thanks for the response will try talking to 
kestrel team.

Original comment by dso...@gmail.com on 9 Dec 2013 at 3:33