Re: local truncate of hints

2013-11-14 Thread Cyril Scetbon 
anyone ?

-- 
Cyril SCETBON

On 10 Nov 2013, at 10:48, Cyril Scetbon  wrote:

> Are you really sure of that ? cause Tracing says the opposite when I do it on 
> one node :
> 
> cqlsh:system> TRUNCATE hints ;
> 
> Tracing session: fe0dbc80-49dd-11e3-a39b-e367b713537d
> 
> activity  
>  | timestamp| source | source_elapsed
> +--++
> 
> execute_cql3_query | 07:59:15,019 |  10.0.0.37 |  0
>   Parsing 
> TRUNCATE hints ; | 07:59:15,020 |  10.0.0.37 |991
>Preparing 
> statement | 07:59:15,021 |  10.0.0.37 |   2009
> Enqueuing truncate messages to hosts [/10.0.0.185, /10.0.0.33, /10.0.0.17, 
> /10.0.0.37] | 07:59:15,023 |  10.0.0.37 |   4459
>   Message received from 
> /10.0.0.37 | 07:59:15,186 |  10.0.0.33 |121
>Applying truncation of 
> system.hints | 07:59:15,200 |  10.0.0.33 |  11064
>  Sending message to 
> /10.0.0.37 | 07:59:15,214 |  10.0.0.37 | 195660
>  Sending message to 
> /10.0.0.33 | 07:59:15,217 |  10.0.0.37 | 198664
>   Message received from 
> /10.0.0.37 | 07:59:15,230 | 10.0.0.185 |149
>Applying truncation of 
> system.hints | 07:59:15,240 | 10.0.0.185 |   6248
>   Message received from 
> /10.0.0.37 | 07:59:15,244 |  10.0.0.17 |117
> Sending message to 
> /10.0.0.185 | 07:59:15,247 |  10.0.0.37 | 134087
>  Sending message to 
> /10.0.0.17 | 07:59:15,248 |  10.0.0.37 | 134760
>   Message received from 
> /10.0.0.37 | 07:59:15,251 |  10.0.0.37 | 232058
>Applying truncation of 
> system.hints | 07:59:15,254 |  10.0.0.37 | 234904
>Applying truncation of 
> system.hints | 07:59:15,259 |  10.0.0.17 |   8574
> Enqueuing response to truncate operation to 
> /10.0.0.37 | 07:59:15,388 |  10.0.0.17 | 144491
>  Sending message to 
> /10.0.0.37 | 07:59:15,389 |  10.0.0.17 | 145341
>   Message received from 
> /10.0.0.17 | 07:59:15,461 |  10.0.0.37 | 441863
>Processing response from 
> /10.0.0.17 | 07:59:15,502 |  10.0.0.37 | 482942
> Enqueuing response to truncate operation to 
> /10.0.0.37 | 07:59:15,578 |  10.0.0.33 | 391940
>  Sending message to 
> /10.0.0.37 | 07:59:15,578 |  10.0.0.33 | 392364
>   Message received from 
> /10.0.0.33 | 07:59:15,632 |  10.0.0.37 | 613172
>Processing response from 
> /10.0.0.33 | 07:59:15,632 |  10.0.0.37 | 613303
> Enqueuing response to truncate operation to 
> /10.0.0.37 | 07:59:15,736 |  10.0.0.37 | 717066
>  Sending message to 
> /10.0.0.37 | 07:59:15,738 |  10.0.0.37 | 719165
>   Message received from 
> /10.0.0.37 | 07:59:15,739 |  10.0.0.37 |   null
>Processing response from 
> /10.0.0.37 | 07:59:15,739 |  10.0.0.37 |   null
> Enqueuing response to truncate operation to 
> /10.0.0.37 | 07:59:15,915 | 10.0.0.185 | 685116
>  Sending message to 
> /10.0.0.37 | 07:59:15,915 | 10.0.0.185 | 685519
>  Message received from 
> /10.0.0.185 | 07:59:15,936 |  10.0.0.37 |   null
>   Processing response from 
> /10.0.0.185 | 07:59:15,936 |  10.0.0.37 |   null
>

Re: local truncate of hints

2013-11-14 Thread Boris Yen 
I quick glimpse at the code. It seems that truncate only cares about if any
node goes down. It does not check the replication strategy.

Boris


On Thu, Nov 14, 2013 at 9:30 PM, Cyril Scetbon wrote:

> anyone ?
>
> --
> Cyril SCETBON
>
> On 10 Nov 2013, at 10:48, Cyril Scetbon  wrote:
>
> > Are you really sure of that ? cause Tracing says the opposite when I do
> it on one node :
> >
> >   cqlsh:system> TRUNCATE hints ;
> >
> > Tracing session: fe0dbc80-49dd-11e3-a39b-e367b713537d
> >
> > activity
>   | timestamp| source | source_elapsed
> >
> +--++
> >
> execute_cql3_query | 07:59:15,019 |  10.0.0.37 |  0
> >   Parsing
> TRUNCATE hints ; | 07:59:15,020 |  10.0.0.37 |991
> >
>  Preparing statement | 07:59:15,021 |  10.0.0.37 |   2009
> > Enqueuing truncate messages to hosts [/10.0.0.185, /10.0.0.33, /
> 10.0.0.17, /10.0.0.37] | 07:59:15,023 |  10.0.0.37 |   4459
> >   Message received
> from /10.0.0.37 | 07:59:15,186 |  10.0.0.33 |121
> >Applying truncation
> of system.hints | 07:59:15,200 |  10.0.0.33 |  11064
> >  Sending message
> to /10.0.0.37 | 07:59:15,214 |  10.0.0.37 | 195660
> >  Sending message
> to /10.0.0.33 | 07:59:15,217 |  10.0.0.37 | 198664
> >   Message received
> from /10.0.0.37 | 07:59:15,230 | 10.0.0.185 |149
> >Applying truncation
> of system.hints | 07:59:15,240 | 10.0.0.185 |   6248
> >   Message received
> from /10.0.0.37 | 07:59:15,244 |  10.0.0.17 |117
> > Sending message
> to /10.0.0.185 | 07:59:15,247 |  10.0.0.37 | 134087
> >  Sending message
> to /10.0.0.17 | 07:59:15,248 |  10.0.0.37 | 134760
> >   Message received
> from /10.0.0.37 | 07:59:15,251 |  10.0.0.37 | 232058
> >Applying truncation
> of system.hints | 07:59:15,254 |  10.0.0.37 | 234904
> >Applying truncation
> of system.hints | 07:59:15,259 |  10.0.0.17 |   8574
> > Enqueuing response to truncate operation
> to /10.0.0.37 | 07:59:15,388 |  10.0.0.17 | 144491
> >  Sending message
> to /10.0.0.37 | 07:59:15,389 |  10.0.0.17 | 145341
> >   Message received
> from /10.0.0.17 | 07:59:15,461 |  10.0.0.37 | 441863
> >Processing response
> from /10.0.0.17 | 07:59:15,502 |  10.0.0.37 | 482942
> > Enqueuing response to truncate operation
> to /10.0.0.37 | 07:59:15,578 |  10.0.0.33 | 391940
> >  Sending message
> to /10.0.0.37 | 07:59:15,578 |  10.0.0.33 | 392364
> >   Message received
> from /10.0.0.33 | 07:59:15,632 |  10.0.0.37 | 613172
> >Processing response
> from /10.0.0.33 | 07:59:15,632 |  10.0.0.37 | 613303
> > Enqueuing response to truncate operation
> to /10.0.0.37 | 07:59:15,736 |  10.0.0.37 | 717066
> >  Sending message
> to /10.0.0.37 | 07:59:15,738 |  10.0.0.37 | 719165
> >   Message received
> from /10.0.0.37 | 07:59:15,739 |  10.0.0.37 |   null
> >Processing response
> from /10.0.0.37 | 07:59:15,739 |  10.0.0.37 |   null
> > Enqueuing response to truncate operation
> to /10.0.0.37 | 07:59:15,915 | 10.0.0.185 | 685116
> >  Sending message
> to /10.0.0.37 | 07:59:15,915 | 10.0.0.185 | 685519
> >  Message received
> from /10.0.0.185 | 07:59:15,936 |  10.0.0.37 |   null
> >   Processing response
> from /10.0.0.185 | 07:59:15,936 |  10.0.0.37 |   null
> >
> Reques

Re: local truncate of hints

2013-11-14 Thread Jonathan Ellis 
You're right.  You'd want to expose the node-local truncate over JMX.

On Sun, Nov 10, 2013 at 3:48 AM, Cyril Scetbon  wrote:
> Are you really sure of that ? cause Tracing says the opposite when I do it on 
> one node :
>
>   cqlsh:system> TRUNCATE hints ;
>
> Tracing session: fe0dbc80-49dd-11e3-a39b-e367b713537d
>
>  activity 
>   | timestamp| source | source_elapsed
> +--++
>  
> execute_cql3_query | 07:59:15,019 |  10.0.0.37 |  0
>Parsing 
> TRUNCATE hints ; | 07:59:15,020 |  10.0.0.37 |991
> Preparing 
> statement | 07:59:15,021 |  10.0.0.37 |   2009
>  Enqueuing truncate messages to hosts [/10.0.0.185, /10.0.0.33, /10.0.0.17, 
> /10.0.0.37] | 07:59:15,023 |  10.0.0.37 |   4459
>Message received from 
> /10.0.0.37 | 07:59:15,186 |  10.0.0.33 |121
> Applying truncation of 
> system.hints | 07:59:15,200 |  10.0.0.33 |  11064
>   Sending message to 
> /10.0.0.37 | 07:59:15,214 |  10.0.0.37 | 195660
>   Sending message to 
> /10.0.0.33 | 07:59:15,217 |  10.0.0.37 | 198664
>Message received from 
> /10.0.0.37 | 07:59:15,230 | 10.0.0.185 |149
> Applying truncation of 
> system.hints | 07:59:15,240 | 10.0.0.185 |   6248
>Message received from 
> /10.0.0.37 | 07:59:15,244 |  10.0.0.17 |117
>  Sending message to 
> /10.0.0.185 | 07:59:15,247 |  10.0.0.37 | 134087
>   Sending message to 
> /10.0.0.17 | 07:59:15,248 |  10.0.0.37 | 134760
>Message received from 
> /10.0.0.37 | 07:59:15,251 |  10.0.0.37 | 232058
> Applying truncation of 
> system.hints | 07:59:15,254 |  10.0.0.37 | 234904
> Applying truncation of 
> system.hints | 07:59:15,259 |  10.0.0.17 |   8574
>  Enqueuing response to truncate operation to 
> /10.0.0.37 | 07:59:15,388 |  10.0.0.17 | 144491
>   Sending message to 
> /10.0.0.37 | 07:59:15,389 |  10.0.0.17 | 145341
>Message received from 
> /10.0.0.17 | 07:59:15,461 |  10.0.0.37 | 441863
> Processing response from 
> /10.0.0.17 | 07:59:15,502 |  10.0.0.37 | 482942
>  Enqueuing response to truncate operation to 
> /10.0.0.37 | 07:59:15,578 |  10.0.0.33 | 391940
>   Sending message to 
> /10.0.0.37 | 07:59:15,578 |  10.0.0.33 | 392364
>Message received from 
> /10.0.0.33 | 07:59:15,632 |  10.0.0.37 | 613172
> Processing response from 
> /10.0.0.33 | 07:59:15,632 |  10.0.0.37 | 613303
>  Enqueuing response to truncate operation to 
> /10.0.0.37 | 07:59:15,736 |  10.0.0.37 | 717066
>   Sending message to 
> /10.0.0.37 | 07:59:15,738 |  10.0.0.37 | 719165
>Message received from 
> /10.0.0.37 | 07:59:15,739 |  10.0.0.37 |   null
> Processing response from 
> /10.0.0.37 | 07:59:15,739 |  10.0.0.37 |   null
>  Enqueuing response to truncate operation to 
> /10.0.0.37 | 07:59:15,915 | 10.0.0.185 | 685116
>   Sending message to 
> /10.0.0.37 | 07:59:15,915 | 10.0.0.185 | 685519
>   Message received from 
> /10.0.0.185 | 07:59:15,936 |  10.0.0.37 |   null
>Processing response from 
> /10.0.0.185 | 07:59:15,936 |  10.0.0.37 |