255d13bdb16e66175c58bf16a15010555e3dced7 Robey Pointer robey@twitter.com http://github.com/dustin/java-memcached-client/commit/c7213d018047b6a17cfac88953e7cacf9ab48b10 c7213d018047b6a17cfac88953e7cacf9ab48b10

2008-10-02T21:49:30-07:00

2008-07-21T16:48:51-07:00

if the memcache server disconnects, try to notice. ba9954495da439d46e78f518eb438f30c6695d24 Dustin Sallings dustin@spy.net e5ebc572775fb7c197381fc5e3d8ffaab3540a9a Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/255d13bdb16e66175c58bf16a15010555e3dced7 255d13bdb16e66175c58bf16a15010555e3dced7

2008-10-02T21:39:57-07:00

Handle fast-failure on an attempted reconnect. http://code.google.com/p/spymemcached/issues/detail?id=31 8b4e359fbc7645e66fa8423108ce881ea85d75d3 Dustin Sallings dustin@spy.net f6d32148d88b1e0f35cdbdc553ce57b1b449aa99 Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/e5ebc572775fb7c197381fc5e3d8ffaab3540a9a e5ebc572775fb7c197381fc5e3d8ffaab3540a9a

2008-10-02T21:22:11-07:00

If we attempt to read when we don't have anything to read, reconnect. This seems to happen in some strange server-error cases where the server short-circuits the connection. This situation has shown itself when we've sent something too large into the server. Precautions have been taken to prevent that exact thing from happening again, but this is a better way to handle an unexpected state. I'm not sure how we end up still having data to receive when we've already thrown away the ops, but tearing down the connection is a clean way to recover from a bad state. b52583e75fb7aabdec5d20dac3147d62d626d8f8 Dustin Sallings dustin@spy.net aa2e8a8bf4b1de88be6715d4dccfee0ef51fbdc5 Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/f6d32148d88b1e0f35cdbdc553ce57b1b449aa99 f6d32148d88b1e0f35cdbdc553ce57b1b449aa99

2008-10-02T20:17:26-07:00

Throw an exception if we attempt to store data we know is too big. This will avoid a few problems people have encountered. I implemented it with a somewhat early IllegalArgumentException because it was the surest way to cover every case given compression and several paths in to sets. 1dcaefeb7569a839d9bf3f65789d5b8b26790101 Dustin Sallings dustin@spy.net 47f15d504960f1779bad1e44275454af05a6a973 Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/aa2e8a8bf4b1de88be6715d4dccfee0ef51fbdc5 aa2e8a8bf4b1de88be6715d4dccfee0ef51fbdc5

2008-10-02T19:47:43-07:00

Fix null handling bug introduced by 6e2dbb3 2b5e34f1e40c33bb73986c29e0d66614adc4f2c5 Dustin Sallings dustin@spy.net 6e2dbb3aac1a2980bc2252670467e219d803a3d8 Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/47f15d504960f1779bad1e44275454af05a6a973 47f15d504960f1779bad1e44275454af05a6a973

2008-10-02T18:50:36-07:00

Minor warning fix. 5605851047864261752d835009c09546f66b7a75 Dustin Sallings dustin@spy.net 0fa9e7d81a07ad73f15f55c0ce68aa5caf9ea087 Kristian Eide kristian@medallia.com http://github.com/dustin/java-memcached-client/commit/6e2dbb3aac1a2980bc2252670467e219d803a3d8 6e2dbb3aac1a2980bc2252670467e219d803a3d8

2008-10-02T11:04:46-07:00

2008-10-02T11:02:54-07:00

Push async get decoding into the client thread instead of the IO thread. 0ee76d51713d90edb61a9f94a0cf2a001f486e37 Dustin Sallings dustin@spy.net 27ad2c39093c14397c5b49a30824997fbee45b1d Nick Brachet nbrachet@gmail.com http://github.com/dustin/java-memcached-client/commit/0fa9e7d81a07ad73f15f55c0ce68aa5caf9ea087 0fa9e7d81a07ad73f15f55c0ce68aa5caf9ea087

2008-09-20T19:56:38-07:00

Default for incr should be a long. 950fbb9acd79450d1d51676239e5bb0a2f7674bc Dustin Sallings dustin@spy.net 02c1f2e02e92dbb47b65a2e73feb62a206f6b433 Nelz nelz9999@gmail.com http://github.com/dustin/java-memcached-client/commit/27ad2c39093c14397c5b49a30824997fbee45b1d 27ad2c39093c14397c5b49a30824997fbee45b1d

2008-09-20T19:43:51-07:00

2008-09-11T15:34:05-07:00

Extract a MemcachedClient interface. An interface enables mocking for any users of the MemcachedClient. 0f3247035b7dccdf49105fdd89d3da43b9d6a5a9 Dustin Sallings dustin@spy.net b10c4a81a92944fc6337f2403042255933122c16 Kristian Eide kristian@medallia.com http://github.com/dustin/java-memcached-client/commit/02c1f2e02e92dbb47b65a2e73feb62a206f6b433 02c1f2e02e92dbb47b65a2e73feb62a206f6b433

2008-08-29T11:46:25-07:00

Decode async bulk gets outside of the IO thread. The same work still needs to happen for one-off gets, but this should help allow the IO thread to focus on IO while consumer threads distribute the more CPU-intensive work. 8db71b4feacd0d682c578fe2796546e8549c7d73 Dustin Sallings dustin@spy.net 919b7323f035a3add0cad3f97404afcfcb9d599e Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/b10c4a81a92944fc6337f2403042255933122c16 b10c4a81a92944fc6337f2403042255933122c16

2008-06-05T22:39:57-07:00

Got build working under buildr 1.3.1.1 8a8f75dfdd08279e704a3d96904a236b0f70910e Dustin Sallings dustin@spy.net 03f8b4301cc4b1bd6924ae02a1c20b14677727a8 Nelz nelz9999@gmail.com http://github.com/dustin/java-memcached-client/commit/919b7323f035a3add0cad3f97404afcfcb9d599e 919b7323f035a3add0cad3f97404afcfcb9d599e

2008-06-05T21:45:26-07:00

More consistent hash proving. f5809e7d83fd198788d72029743905409ec3f51d Dustin Sallings dustin@spy.net 687aa9ccc1c9361b2cd6f1d769e70e4438d98d9f Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/03f8b4301cc4b1bd6924ae02a1c20b14677727a8 03f8b4301cc4b1bd6924ae02a1c20b14677727a8

2008-05-27T00:06:45-07:00

2008-05-26T23:57:28-07:00

Killed off a slightly elusive bug that was causing sporatic cancellations. Whenever a read returned in the binary protocol without having read enough bytes to fill a header packet, an NPE would be fired that would cause us to disconnect from the server and cancel all in-flight operations. This happened occasionally in one of my tests and was rather a pain to track down. It likely never affected anyone since I doubt anyone is actually using the binary protocol anywhere today. 772c6ee70e499ea6c0acf12fdff91724093034fc Dustin Sallings dustin@spy.net 3d806bac909790a0fee4c655a5d005ecd30d464a Nelz nelz9999@gmail.com http://github.com/dustin/java-memcached-client/commit/687aa9ccc1c9361b2cd6f1d769e70e4438d98d9f 687aa9ccc1c9361b2cd6f1d769e70e4438d98d9f

2008-05-27T00:06:45-07:00

2008-05-16T12:02:25-07:00

Adding a standard ConnectionFactory to facilitate consistent hashing. e4eb1a5efa8a8cf749bcea194f0b84c14128d6c3 Dustin Sallings dustin@spy.net 9de48599d5a18cb5d59779e7c28713b517285aa4 Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/3d806bac909790a0fee4c655a5d005ecd30d464a 3d806bac909790a0fee4c655a5d005ecd30d464a

2008-05-14T09:28:35-07:00

Allow the input, op read and op write queues to be individually specified. By default, the read queue is 10% larger than the input queue. With a sufficiently large op read queue, it's possible to never internally overflow, but correct values are likely application-specific. 1a962e56e4b4c20821286a2280e919aa1e648e0f Dustin Sallings dustin@spy.net f1969bf1f88b62a71dcc9f392c4c9f0756fcea09 Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/9de48599d5a18cb5d59779e7c28713b517285aa4 9de48599d5a18cb5d59779e7c28713b517285aa4

2008-05-13T22:41:39-07:00

Updated delete documentation. 650180506dee0d0caf6d3470c80149565588642a Dustin Sallings dustin@spy.net 0be1844a79e2d9ecd635e770faf479f3a221be87 Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/f1969bf1f88b62a71dcc9f392c4c9f0756fcea09 f1969bf1f88b62a71dcc9f392c4c9f0756fcea09

2008-05-13T22:20:37-07:00

2008-05-13T22:19:42-07:00

Some refactoring in the futures to get more consistent behavior. 8aafba90a32922014e8babb98c2af083de0fcd09 Dustin Sallings dustin@spy.net 6a38bf7b3b190035e35133e8b08056ceb86d2eaf Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/0be1844a79e2d9ecd635e770faf479f3a221be87 0be1844a79e2d9ecd635e770faf479f3a221be87

2008-05-13T22:20:37-07:00

2008-05-13T22:18:58-07:00

Read before writes and expect IllegalStateException. These are two measures that are helping with the queue overflow problems. Firstly, the IllegalStateException is thrown whenever you attempted to add to a queue that's full. If that happens internally, I don't want the IO thread to crash, so I add it to the normal ``expected exceptions'' list. Secondly, reading before writing helps keep the read buffer ready for new data. When writing first, the write will have to transition to a read and may cause the read buffer to overflow. It still may happen, but by servicing the reads first I can at least get the complete ones popped out before piling new ones in (since writes are almost always smaller and likely to transition). f17bbf319e48839119dfef8e39f58803338dbb87 Dustin Sallings dustin@spy.net d578d1b1931cfdf006190c034b7d7cc4fba84efd Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/6a38bf7b3b190035e35133e8b08056ceb86d2eaf 6a38bf7b3b190035e35133e8b08056ceb86d2eaf

2008-05-13T22:20:36-07:00

2008-05-13T20:52:11-07:00

Tests for queue overflow behavior. b85a2dd4a47e911ba0ac5845a0aaf40e66174a89 Dustin Sallings dustin@spy.net f96758feb52f4e145aeac02e78b16faaa42dd37e Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/d578d1b1931cfdf006190c034b7d7cc4fba84efd d578d1b1931cfdf006190c034b7d7cc4fba84efd

2008-05-12T23:06:02-07:00

Some fixups from bug 24 relating to overfilling queues. 76cc4fda1553c0a20ea85828335a7aed2ade41dc Dustin Sallings dustin@spy.net 6002b14da1adb1460d10c7cdee79c0e56e1e6dad Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/f96758feb52f4e145aeac02e78b16faaa42dd37e f96758feb52f4e145aeac02e78b16faaa42dd37e

2008-05-11T01:04:16-07:00

2008-05-11T00:58:12-07:00

Update the buildr version number -- always forget that. 0a0f19cd83ed87fd6c4ffa12f4ca288c2aca5f16 Dustin Sallings dustin@spy.net 0f182a56f902a19aed731e636306e89a54bc652d Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/6002b14da1adb1460d10c7cdee79c0e56e1e6dad 6002b14da1adb1460d10c7cdee79c0e56e1e6dad

2008-05-11T00:37:16-07:00

Lengthen the timeout in the text protocol test to match the binary. 83a47a34abd590baa6277a5a0d9319a3c8d67329 Dustin Sallings dustin@spy.net 1716023576970f56e98e1f4d92df4ed9bcb5b720 Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/0f182a56f902a19aed731e636306e89a54bc652d 0f182a56f902a19aed731e636306e89a54bc652d

2008-05-11T00:34:27-07:00

Turning the timeouts way up during tests. I manage to do something that slows stuff down in my full test plan which leads to spurious failures. This may be hinting at a bug of some type, or perhaps some bad defaults, but this code isn't attempting to test timeouts so they should never get in the way. 26426786acf64d09813d8ac055bf488a54bf5d2c Dustin Sallings dustin@spy.net 04df553918fd718eabb031c7084ea272e81fd50c Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/1716023576970f56e98e1f4d92df4ed9bcb5b720 1716023576970f56e98e1f4d92df4ed9bcb5b720

2008-05-11T00:07:46-07:00

buildr 1.3 is not ready for me. Revert "Updates for a newer version of buildr." This reverts commit 0fcb055473fd567308b8c17edec4bdfbd1df6f32. 9a647e3919c2136a8c06346d0bc9719ee246668b Dustin Sallings dustin@spy.net 1d71864711c4135956e4bbbebc14135eb0ec8373 Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/04df553918fd718eabb031c7084ea272e81fd50c 04df553918fd718eabb031c7084ea272e81fd50c

2008-05-10T22:28:49-07:00

Smarter assertion check test. The previous one passing when assertions weren't enabled. Must test the tests. 3c0adb8d7fa698e4f5593236948558d5b686475e Dustin Sallings dustin@spy.net 0fcb055473fd567308b8c17edec4bdfbd1df6f32 Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/1d71864711c4135956e4bbbebc14135eb0ec8373 1d71864711c4135956e4bbbebc14135eb0ec8373

2008-05-10T19:09:57-07:00

Test fix. Invalid connections shouldn't fail to shut down. I think there may be a bigger bug around this, but it only occurs when trying to shut down a connection that shouldn't've started due to someone writing a broken connection factory, so I think we can live with it. 6348a8b2b6b6697aba1bc50e4818ffc5b445f484 Dustin Sallings dustin@spy.net dbf7040ecb19139729f9308205aa3aacef3954cb Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/0fcb055473fd567308b8c17edec4bdfbd1df6f32 0fcb055473fd567308b8c17edec4bdfbd1df6f32

2008-05-09T11:11:32-07:00

Updates for a newer version of buildr. 6218288383e18c576c429df29c67f872f6f4cee0 Dustin Sallings dustin@spy.net 2603ac25e863283170eb42e5bfc3a29eedf30a07 Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/dbf7040ecb19139729f9308205aa3aacef3954cb dbf7040ecb19139729f9308205aa3aacef3954cb

2008-05-04T23:08:38-07:00

2008-05-04T19:41:24-07:00

Disabled test that spuriously fails. b1d480b556525d4eb065b8b748cbf630d7306088 Dustin Sallings dustin@spy.net 57ccff1274aa4bd921260fdd41ee2e537e7d2cc1 Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/2603ac25e863283170eb42e5bfc3a29eedf30a07 2603ac25e863283170eb42e5bfc3a29eedf30a07

2008-05-03T16:48:44-07:00

Wrote a test for async get bulk with a transcoder. e10c59ffe750fe4babe04f8472512a53453f3719 Dustin Sallings dustin@spy.net 7c7be67005944f044760a7217d2b0dd86c46636d Dustin Sallings dustin@spy.net http://github.com/dustin/java-memcached-client/commit/57ccff1274aa4bd921260fdd41ee2e537e7d2cc1 57ccff1274aa4bd921260fdd41ee2e537e7d2cc1

2008-05-03T16:44:47-07:00

2008-05-03T16:44:31-07:00

Make sure all of the CASMutator constructors are at least run once. 8f058e35147d369bd5bfa61f16cb0a536cfb37a6 Dustin Sallings dustin@spy.net