50100 inserts or deletes? also how much ram / cpu do you have on the server running this, and what's the ram / cpu usage at about the time it fails?
On Tue, Mar 24, 2015 at 5:29 PM, joss Earl <j...@rareformnewmedia.com> wrote: > on a stock install, it gets to about 50100 before grinding to a halt > > > > On 24 March 2015 at 12:19, Ali Akhtar <ali.rac...@gmail.com> wrote: > >> What happens when you run it? How far does it get before stopping? >> >> On Tue, Mar 24, 2015 at 5:13 PM, joss Earl <j...@rareformnewmedia.com> >> wrote: >> >>> sure: https://gist.github.com/joss75321/7d85e4c75c06530e9d80 >>> >>> On 24 March 2015 at 12:04, Ali Akhtar <ali.rac...@gmail.com> wrote: >>> >>>> Can you put your code on gist.github.com or pastebin? >>>> >>>> On Tue, Mar 24, 2015 at 4:58 PM, joss Earl <j...@rareformnewmedia.com> >>>> wrote: >>>> >>>>> I run into trouble after a while if I delete rows, this happens in >>>>> both 2.1.3 and 2.0.13, and I encountered the same problem when using >>>>> either >>>>> the datastax java driver or the stock python driver. >>>>> The problem is reproducible using the attached python program. >>>>> >>>>> Once the problem is encountered, the table becomes unusable.. >>>>> >>>>> cqlsh:test1> select id from msg limit 1; >>>>> Request did not complete within rpc_timeout. >>>>> >>>>> So, questions are: >>>>> am I doing something wrong ? >>>>> is this expected behaviour ? >>>>> is there some way to fix the table and make it usable again once this >>>>> has happened ? >>>>> if this is a bug, what is the best way of reporting it ? >>>>> >>>>> Many thanks >>>>> Joss >>>>> >>>> >>>> >>> >> >
