Re: (C)* stable version after 3.5

[Tyler Hobbs]

On Wed, Jul 13, 2016 at 11:32 AM, Anuj Wadehra 
wrote:

> Why do you think that skipping 2.2 is not recommended when NEWS.txt
> suggests otherwise? Can you elaborate?


We test upgrading from 2.1 -> 3.x and upgrading from 2.2 -> 3.x
equivalently.  There should not be a difference in terms of how well the
upgrade is supported.


-- 
Tyler Hobbs
DataStax 

Re: Is my cluster normal?

[Yuan Fang]

In addition, it seems the compaction is very often. It happens like every
couple of seconds and one after one. It seems causing high load.

On Wed, Jul 13, 2016 at 10:32 AM, Yuan Fang  wrote:

> $nodetool tpstats
>
> ...
> Pool Name   Active   Pending   Completed
> Blocked  All time blocked
> Native-Transport-Requests   128   1281420623949 1
> 142821509
> ...
>
>
>
> What is this? Is it normal?
>
> On Tue, Jul 12, 2016 at 3:03 PM, Yuan Fang  wrote:
>
>> Hi Jonathan,
>>
>> Here is the result:
>>
>> ubuntu@ip-172-31-44-250:~$ iostat -dmx 2 10
>> Linux 3.13.0-74-generic (ip-172-31-44-250) 07/12/2016 _x86_64_ (4 CPU)
>>
>> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s
>> avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
>> xvda  0.01 2.130.741.55 0.01 0.02
>>  27.77 0.000.740.890.66   0.43   0.10
>> xvdf  0.01 0.58  237.41   52.5012.90 6.21
>> 135.02 2.328.013.65   27.72   0.57  16.63
>>
>> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s
>> avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
>> xvda  0.00 7.500.002.50 0.00 0.04
>>  32.00 0.001.600.001.60   1.60   0.40
>> xvdf  0.00 0.00  353.500.0024.12 0.00
>> 139.75 0.491.371.370.00   0.58  20.60
>>
>> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s
>> avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
>> xvda  0.00 0.000.001.00 0.00 0.00
>> 8.00 0.000.000.000.00   0.00   0.00
>> xvdf  0.00 2.00  463.50   35.0030.69 2.86
>> 137.84 0.881.771.298.17   0.60  30.00
>>
>> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s
>> avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
>> xvda  0.00 0.000.001.00 0.00 0.00
>> 8.00 0.000.000.000.00   0.00   0.00
>> xvdf  0.00 0.00   99.50   36.00 8.54 4.40
>> 195.62 1.553.881.45   10.61   1.06  14.40
>>
>> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s
>> avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
>> xvda  0.00 5.000.001.50 0.00 0.03
>>  34.67 0.001.330.001.33   1.33   0.20
>> xvdf  0.00 1.50  703.00  195.0048.8323.76
>> 165.57 6.498.361.66   32.51   0.55  49.80
>>
>> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s
>> avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
>> xvda  0.00 0.000.001.00 0.00 0.04
>>  72.00 0.000.000.000.00   0.00   0.00
>> xvdf  0.00 2.50  149.50   69.5010.12 6.68
>> 157.14 0.743.421.188.23   0.51  11.20
>>
>> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s
>> avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
>> xvda  0.00 5.000.002.50 0.00 0.03
>>  24.00 0.000.000.000.00   0.00   0.00
>> xvdf  0.00 0.00   61.50   22.50 5.36 2.75
>> 197.64 0.333.931.50   10.58   0.88   7.40
>>
>> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s
>> avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
>> xvda  0.00 0.000.000.50 0.00 0.00
>> 8.00 0.000.000.000.00   0.00   0.00
>> xvdf  0.00 0.00  375.000.0024.84 0.00
>> 135.64 0.451.201.200.00   0.57  21.20
>>
>> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s
>> avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
>> xvda  0.00 1.000.006.00 0.00 0.03
>> 9.33 0.000.000.000.00   0.00   0.00
>> xvdf  0.00 0.00  542.50   23.5035.08 2.83
>> 137.16 0.801.411.157.23   0.49  28.00
>>
>> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s
>> avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
>> xvda  0.00 3.500.501.50 0.00 0.02
>>  24.00 0.000.000.000.00   0.00   0.00
>> xvdf  0.00 1.50  272.00  153.5016.1818.67
>> 167.7314.32   33.661.39   90.84   0.81  34.60
>>
>>
>>
>> On Tue, Jul 12, 2016 at 12:34 PM, Jonathan Haddad 
>> wrote:
>>
>>> When you have high system load it means your CPU is waiting for
>>> *something*, and in my experience it's usually slow disk.  A disk connected
>>> over network has been a culprit for me many times.
>>>
>>> On Tue, Jul 12, 2016 at 12:33 PM Jonathan Haddad 
>>> wrote:
>>>
 Can do you do:

 iostat -dmx 2 10

Re: Is my cluster normal?

[Yuan Fang]

$nodetool tpstats

...
Pool Name   Active   Pending   Completed
Blocked  All time blocked
Native-Transport-Requests   128   1281420623949 1
  142821509
...



What is this? Is it normal?

On Tue, Jul 12, 2016 at 3:03 PM, Yuan Fang  wrote:

> Hi Jonathan,
>
> Here is the result:
>
> ubuntu@ip-172-31-44-250:~$ iostat -dmx 2 10
> Linux 3.13.0-74-generic (ip-172-31-44-250) 07/12/2016 _x86_64_ (4 CPU)
>
> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s avgrq-sz
> avgqu-sz   await r_await w_await  svctm  %util
> xvda  0.01 2.130.741.55 0.01 0.0227.77
> 0.000.740.890.66   0.43   0.10
> xvdf  0.01 0.58  237.41   52.5012.90 6.21   135.02
> 2.328.013.65   27.72   0.57  16.63
>
> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s avgrq-sz
> avgqu-sz   await r_await w_await  svctm  %util
> xvda  0.00 7.500.002.50 0.00 0.0432.00
> 0.001.600.001.60   1.60   0.40
> xvdf  0.00 0.00  353.500.0024.12 0.00   139.75
> 0.491.371.370.00   0.58  20.60
>
> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s avgrq-sz
> avgqu-sz   await r_await w_await  svctm  %util
> xvda  0.00 0.000.001.00 0.00 0.00 8.00
> 0.000.000.000.00   0.00   0.00
> xvdf  0.00 2.00  463.50   35.0030.69 2.86   137.84
> 0.881.771.298.17   0.60  30.00
>
> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s avgrq-sz
> avgqu-sz   await r_await w_await  svctm  %util
> xvda  0.00 0.000.001.00 0.00 0.00 8.00
> 0.000.000.000.00   0.00   0.00
> xvdf  0.00 0.00   99.50   36.00 8.54 4.40   195.62
> 1.553.881.45   10.61   1.06  14.40
>
> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s avgrq-sz
> avgqu-sz   await r_await w_await  svctm  %util
> xvda  0.00 5.000.001.50 0.00 0.0334.67
> 0.001.330.001.33   1.33   0.20
> xvdf  0.00 1.50  703.00  195.0048.8323.76   165.57
> 6.498.361.66   32.51   0.55  49.80
>
> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s avgrq-sz
> avgqu-sz   await r_await w_await  svctm  %util
> xvda  0.00 0.000.001.00 0.00 0.0472.00
> 0.000.000.000.00   0.00   0.00
> xvdf  0.00 2.50  149.50   69.5010.12 6.68   157.14
> 0.743.421.188.23   0.51  11.20
>
> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s avgrq-sz
> avgqu-sz   await r_await w_await  svctm  %util
> xvda  0.00 5.000.002.50 0.00 0.0324.00
> 0.000.000.000.00   0.00   0.00
> xvdf  0.00 0.00   61.50   22.50 5.36 2.75   197.64
> 0.333.931.50   10.58   0.88   7.40
>
> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s avgrq-sz
> avgqu-sz   await r_await w_await  svctm  %util
> xvda  0.00 0.000.000.50 0.00 0.00 8.00
> 0.000.000.000.00   0.00   0.00
> xvdf  0.00 0.00  375.000.0024.84 0.00   135.64
> 0.451.201.200.00   0.57  21.20
>
> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s avgrq-sz
> avgqu-sz   await r_await w_await  svctm  %util
> xvda  0.00 1.000.006.00 0.00 0.03 9.33
> 0.000.000.000.00   0.00   0.00
> xvdf  0.00 0.00  542.50   23.5035.08 2.83   137.16
> 0.801.411.157.23   0.49  28.00
>
> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s avgrq-sz
> avgqu-sz   await r_await w_await  svctm  %util
> xvda  0.00 3.500.501.50 0.00 0.0224.00
> 0.000.000.000.00   0.00   0.00
> xvdf  0.00 1.50  272.00  153.5016.1818.67   167.73
>14.32   33.661.39   90.84   0.81  34.60
>
>
>
> On Tue, Jul 12, 2016 at 12:34 PM, Jonathan Haddad 
> wrote:
>
>> When you have high system load it means your CPU is waiting for
>> *something*, and in my experience it's usually slow disk.  A disk connected
>> over network has been a culprit for me many times.
>>
>> On Tue, Jul 12, 2016 at 12:33 PM Jonathan Haddad 
>> wrote:
>>
>>> Can do you do:
>>>
>>> iostat -dmx 2 10
>>>
>>>
>>>
>>> On Tue, Jul 12, 2016 at 11:20 AM Yuan Fang 
>>> wrote:
>>>
 Hi Jeff,

 The read being low is because we do not have much read operations right
 now.

 The heap is only 4GB.

 MAX_HEAP_SIZE=4GB

 On Thu, Jul 7, 

Re: CPU high load

[Patrick McFadin]

Might be more clear looking at nodetool tpstats

>From there you can see all the thread pools and if there are any blocks.
Could be something subtle like network.

On Tue, Jul 12, 2016 at 3:23 PM, Aoi Kadoya  wrote:

> Hi,
>
> I am running 6 nodes vnode cluster with DSE 4.8.1, and since few weeks
> ago, all of the cluster nodes are hitting avg. 15-20 cpu load.
> These nodes are running on VMs(VMware vSphere) that have 8vcpu
> (1core/socket)-16 vRAM.(JVM options : -Xms8G -Xmx8G -Xmn800M)
>
> At first I thought this is because of CPU iowait, however, iowait is
> constantly low(in fact it's 0 almost all time time), CPU steal time is
> also 0%.
>
> When I took a thread dump, I found some of "SharedPool-Worker" threads
> are consuming CPU and those threads seem to be waiting for something
> so I assume this is the cause of cpu load.
>
> "SharedPool-Worker-1" #240 daemon prio=5 os_prio=0
> tid=0x7fabf459e000 nid=0x39b3 waiting on condition
> [0x7faad7f02000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:85)
> at java.lang.Thread.run(Thread.java:745)
>
> Thread dump looks like this, but I am not sure what is this
> sharedpool-worker waiting for.
> Would you please help me with the further trouble shooting?
> I am also reading the thread posted by Yuan as the situation is very
> similar to mine but I didn't get any blocked, dropped or pending count
> in my tpstat result.
>
> Thanks,
> Aoi
>

Re: (C)* stable version after 3.5

[Anuj Wadehra]

Hi Alain,
This caught my attention:
"Also I am not sure if the 2.2 major version is something you can skip while 
upgrading through a rolling restart. I believe you can, but it is not what is 
recommended."

Why do you think that skipping 2.2 is not recommended when NEWS.txt suggests 
otherwise? Can you elaborate?

ThanksAnuj

 
 
  On Tue, 12 Jul, 2016 at 7:31 PM, Alain RODRIGUEZ wrote:   
Hi,
The only "fix" release after 3.5 is 3.7. Yet hard to say if it is more stable, 
we can hope so.
For Tic-Toc releases (on 3.X)
Odd numbers are fix releases.
Even numbers are feature releases.
Not sure why you want something above 3.5, but take care, those versions are 
really recent, and less tested so maybe not that "stable". If you want 
something more stable, I believe you can go with 3.0.8.
Yet I am not telling you not to do that, some people need to start testing new 
things right... So if you choose 3.7 because you want some feature from there, 
it is perfectly ok, just move carefully, maybe read some opened tickets and 
previous experiences from the community and test the upgrade process first on a 
dev cluster.
Also I am not sure if the 2.2 major version is something you can skip while 
upgrading through a rolling restart. I believe you can, but it is not what is 
recommended. Testing will let you know anyway.
Good luck and tell us how it went :-).
C*heers,---Alain Rodriguez - alain@thelastpickle.comFrance
The Last Pickle - Apache Cassandra Consultinghttp://www.thelastpickle.com
2016-07-12 11:05 GMT+02:00 Varun Barala :

Hi all users,


Currently we are using cassandra-2.1.13 but we want to upgrade 2.1.13 to 3.x in 
production.

Could anyone please tell me which is the most stable cassandra version after 
3.5.

Thanking You!!


Regards,
Varun Barala

  

Re: NoHostAvailableException coming up on our server

[Romain Hardouin]

Put the driver logs in debug mode to see what's happen.Btw I am surprised by 
the few requests by connections in your setup:
.setConnectionsPerHost(HostDistance.LOCAL, 20, 20)
 .setMaxRequestsPerConnection(HostDistance.LOCAL, 128) It looks like a 
protocol v2 settings (Cassandra 2.0) because it was limited to 128 requests per 
connection. You're using C* 3.3 so the protocol v4.You can go up to 32K since 
protocol v3. As a first step I would try to open only 2 connections with 16K in 
MaxRequestsPerConnection. Then try to fine tune.
Best,
Romain

Le Mardi 12 juillet 2016 23h57, Abhinav Solan  a 
écrit :
 

 I am using 3.0.0 version over apache-cassandra-3.3 
On Tue, Jul 12, 2016 at 2:37 PM Riccardo Ferrari  wrote:

What driver version are you using?
You can look at the LoggingRetryPolicy to have more meaningful messages in your 
logs.
best,
On Tue, Jul 12, 2016 at 9:02 PM, Abhinav Solan  wrote:

Thanks, JohnnyActually, they were running .. it went through a series of read 
and writes .. and recovered after the error.Is there any settings I can specify 
in preparing the Session at java client driver level, here are my current 
settings - PoolingOptions poolingOptions = new PoolingOptions()
 .setConnectionsPerHost(HostDistance.LOCAL, 20, 20)
 .setMaxRequestsPerConnection(HostDistance.LOCAL, 128)
 .setNewConnectionThreshold(HostDistance.LOCAL, 100);

 Cluster.Builder builder = Cluster.builder()
 .addContactPoints(cp)
 .withPoolingOptions(poolingOptions)
 .withProtocolVersion(ProtocolVersion.NEWEST_SUPPORTED)
 .withPort(port);

On Tue, Jul 12, 2016 at 11:47 AM Johnny Miller  
wrote:

Abhinav - your getting that as the driver isn’t finding any hosts up for your 
query. You probably need to check if all the nodes in your cluster are running.
See: 
http://docs.datastax.com/en/drivers/java/3.0/com/datastax/driver/core/exceptions/NoHostAvailableException.html

Johnny

On 12 Jul 2016, at 18:46, Abhinav Solan  wrote:
Hi Everyone,
I am getting this error on our server, it comes and goes seems the connection 
drops a comes back after a while -Caused by: 
com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried 
for query failed (tried: :9042 
(com.datastax.driver.core.exceptions.ConnectionException: [] 
Pool is CLOSING))
at 
com.datastax.driver.core.RequestHandler.reportNoMoreHosts(RequestHandler.java:218)
at 
com.datastax.driver.core.RequestHandler.access$1000(RequestHandler.java:43)
at 
com.datastax.driver.core.RequestHandler$SpeculativeExecution.sendRequest(RequestHandler.java:284)
at 
com.datastax.driver.core.RequestHandler.startNewExecution(RequestHandler.java:115)
at 
com.datastax.driver.core.RequestHandler.sendRequest(RequestHandler.java:91)
at 
com.datastax.driver.core.SessionManager.executeAsync(SessionManager.java:129)Can
 anyone suggest me what can be done to handle this error ? 
Thanks,Abhinav







  

Re: Is my cluster normal?

[Yuan Fang]

Sometimes, the Pending can change from 128 to 129, 125 etc.


On Wed, Jul 13, 2016 at 10:32 AM, Yuan Fang  wrote:

> $nodetool tpstats
>
> ...
> Pool Name   Active   Pending   Completed
> Blocked  All time blocked
> Native-Transport-Requests   128   1281420623949 1
> 142821509
> ...
>
>
>
> What is this? Is it normal?
>
> On Tue, Jul 12, 2016 at 3:03 PM, Yuan Fang  wrote:
>
>> Hi Jonathan,
>>
>> Here is the result:
>>
>> ubuntu@ip-172-31-44-250:~$ iostat -dmx 2 10
>> Linux 3.13.0-74-generic (ip-172-31-44-250) 07/12/2016 _x86_64_ (4 CPU)
>>
>> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s
>> avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
>> xvda  0.01 2.130.741.55 0.01 0.02
>>  27.77 0.000.740.890.66   0.43   0.10
>> xvdf  0.01 0.58  237.41   52.5012.90 6.21
>> 135.02 2.328.013.65   27.72   0.57  16.63
>>
>> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s
>> avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
>> xvda  0.00 7.500.002.50 0.00 0.04
>>  32.00 0.001.600.001.60   1.60   0.40
>> xvdf  0.00 0.00  353.500.0024.12 0.00
>> 139.75 0.491.371.370.00   0.58  20.60
>>
>> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s
>> avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
>> xvda  0.00 0.000.001.00 0.00 0.00
>> 8.00 0.000.000.000.00   0.00   0.00
>> xvdf  0.00 2.00  463.50   35.0030.69 2.86
>> 137.84 0.881.771.298.17   0.60  30.00
>>
>> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s
>> avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
>> xvda  0.00 0.000.001.00 0.00 0.00
>> 8.00 0.000.000.000.00   0.00   0.00
>> xvdf  0.00 0.00   99.50   36.00 8.54 4.40
>> 195.62 1.553.881.45   10.61   1.06  14.40
>>
>> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s
>> avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
>> xvda  0.00 5.000.001.50 0.00 0.03
>>  34.67 0.001.330.001.33   1.33   0.20
>> xvdf  0.00 1.50  703.00  195.0048.8323.76
>> 165.57 6.498.361.66   32.51   0.55  49.80
>>
>> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s
>> avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
>> xvda  0.00 0.000.001.00 0.00 0.04
>>  72.00 0.000.000.000.00   0.00   0.00
>> xvdf  0.00 2.50  149.50   69.5010.12 6.68
>> 157.14 0.743.421.188.23   0.51  11.20
>>
>> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s
>> avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
>> xvda  0.00 5.000.002.50 0.00 0.03
>>  24.00 0.000.000.000.00   0.00   0.00
>> xvdf  0.00 0.00   61.50   22.50 5.36 2.75
>> 197.64 0.333.931.50   10.58   0.88   7.40
>>
>> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s
>> avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
>> xvda  0.00 0.000.000.50 0.00 0.00
>> 8.00 0.000.000.000.00   0.00   0.00
>> xvdf  0.00 0.00  375.000.0024.84 0.00
>> 135.64 0.451.201.200.00   0.57  21.20
>>
>> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s
>> avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
>> xvda  0.00 1.000.006.00 0.00 0.03
>> 9.33 0.000.000.000.00   0.00   0.00
>> xvdf  0.00 0.00  542.50   23.5035.08 2.83
>> 137.16 0.801.411.157.23   0.49  28.00
>>
>> Device: rrqm/s   wrqm/s r/s w/srMB/swMB/s
>> avgrq-sz avgqu-sz   await r_await w_await  svctm  %util
>> xvda  0.00 3.500.501.50 0.00 0.02
>>  24.00 0.000.000.000.00   0.00   0.00
>> xvdf  0.00 1.50  272.00  153.5016.1818.67
>> 167.7314.32   33.661.39   90.84   0.81  34.60
>>
>>
>>
>> On Tue, Jul 12, 2016 at 12:34 PM, Jonathan Haddad 
>> wrote:
>>
>>> When you have high system load it means your CPU is waiting for
>>> *something*, and in my experience it's usually slow disk.  A disk connected
>>> over network has been a culprit for me many times.
>>>
>>> On Tue, Jul 12, 2016 at 12:33 PM Jonathan Haddad 
>>> wrote:
>>>
 Can do you do:

 iostat -dmx 2 10



 On Tue, Jul 12, 2016 at 11:20 AM Yuan Fang 

ApacheCon: Getting the word out internally

[Melissa Warnkin]

Dear Apache Enthusiast,

As you are no doubt already aware, we will be holding ApacheCon in
Seville, Spain, the week of November 14th, 2016. The call for papers
(CFP) for this event is now open, and will remain open until
September 9th.

The event is divided into two parts, each with its own CFP. The first
part of the event, called Apache Big Data, focuses on Big Data
projects and related technologies.

Website: http://events.linuxfoundation.org/events/apache-big-data-europe
CFP:
http://events.linuxfoundation.org/events/apache-big-data-europe/program/cfp

The second part, called ApacheCon Europe, focuses on the Apache
Software Foundation as a whole, covering all projects, community
issues, governance, and so on.

Website: http://events.linuxfoundation.org/events/apachecon-europe
CFP: http://events.linuxfoundation.org/events/apachecon-europe/program/cfp

ApacheCon is the official conference of the Apache Software
Foundation, and is the best place to meet members of your project and
other ASF projects, and strengthen your project's community.

If your organization is interested in sponsoring ApacheCon, contact me
at e...@apache.org  ApacheCon is a great place to find the brightest
developers in the world, and experts on a huge range of technologies.

I hope to see you in Seville!
==

Melissaon behalf of the ApacheCon Team

Re: CPU high load

[Aoi Kadoya]

Hi Patrick,

In fact I couldn't see any thread pool named "shared".
here is the result of tpstats from one of my nodes.

Pool NameActive   Pending  Completed   Blocked
 All time blocked
MutationStage 0 0  173237609 0
0
ReadStage 0 0   71266557 0
0
RequestResponseStage  0 0   87617557 0
0
ReadRepairStage   0 0  51822 0
0
CounterMutationStage  0 0  0 0
0
MiscStage 0 0  0 0
0
AntiEntropySessions   0 0   3828 0
0
HintedHandoff 0 0 23 0
0
GossipStage   0 02169599 0
0
CacheCleanupExecutor  0 0  0 0
0
InternalResponseStage 0 0  0 0
0
CommitLogArchiver 0 0  0 0
0
CompactionExecutor0 01353194 0
0
ValidationExecutor0 03337647 0
0
MigrationStage0 0  5 0
0
AntiEntropyStage  0 07527026 0
0
PendingRangeCalculator0 0 24 0
0
Sampler   0 0  0 0
0
MemtableFlushWriter   0 0 118019 0
0
MemtablePostFlush 0 03398738 0
0
MemtableReclaimMemory 0 0 122249 0
0

Message type   Dropped
READ 0
RANGE_SLICE  0
_TRACE   0
MUTATION 0
COUNTER_MUTATION 0
BINARY   0
REQUEST_RESPONSE 0
PAGED_RANGE  0
READ_REPAIR  0


I have enabled a auto repair service on opscenter and it's running
behind but I also realized that my cluster isn't well balanced..
other than system/opscenter keyspaces, I only have one keyspace and
its replication factor is 3 (network topology strategy)

Datacenter: xxx

Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address Load   Tokens  OwnsHost ID
  Rack
UN  xx  10.19 GB   256 ?
6bf8db87-d4cc-4a75-86a5-bc1b27ced32c  RAC1
UN  xx   10.59 GB   256 ?
2d407831-e10d-4a6b-86c0-26c7a60e613d  RAC1
UN  xx   7.99 GB256 ?
1e05d70e-502e-4ac4-a6ed-bf912c332062  RAC1
UN  xx   7.67 GB256 ?
41a8e12a-c8e8-42ff-b681-b74f493a2407  RAC1
UN  xx   11.13 GB   256 ?
67572986-99b8-4a78-9039-aaa0aca8c236  RAC1
UN  xx   9.54 GB256 ?
3f22001b-f03d-4bd0-8608-dd467cbc17f0  RAC1

Thanks,
Aoi

2016-07-13 9:15 GMT-07:00 Patrick McFadin :
> Might be more clear looking at nodetool tpstats
>
> From there you can see all the thread pools and if there are any blocks.
> Could be something subtle like network.
>
> On Tue, Jul 12, 2016 at 3:23 PM, Aoi Kadoya  wrote:
>>
>> Hi,
>>
>> I am running 6 nodes vnode cluster with DSE 4.8.1, and since few weeks
>> ago, all of the cluster nodes are hitting avg. 15-20 cpu load.
>> These nodes are running on VMs(VMware vSphere) that have 8vcpu
>> (1core/socket)-16 vRAM.(JVM options : -Xms8G -Xmx8G -Xmn800M)
>>
>> At first I thought this is because of CPU iowait, however, iowait is
>> constantly low(in fact it's 0 almost all time time), CPU steal time is
>> also 0%.
>>
>> When I took a thread dump, I found some of "SharedPool-Worker" threads
>> are consuming CPU and those threads seem to be waiting for something
>> so I assume this is the cause of cpu load.
>>
>> "SharedPool-Worker-1" #240 daemon prio=5 os_prio=0
>> tid=0x7fabf459e000 nid=0x39b3 waiting on condition
>> [0x7faad7f02000]
>>java.lang.Thread.State: WAITING (parking)
>> at sun.misc.Unsafe.park(Native Method)
>> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
>> at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:85)
>> at java.lang.Thread.run(Thread.java:745)
>>
>> Thread dump looks like this, but I am not sure what is this
>> sharedpool-worker waiting for.
>> Would you please help me with the further trouble shooting?
>> I am also reading the thread posted by Yuan as the situation is very
>> similar to mine but I didn't get any blocked, dropped or pending count
>> in my tpstat result.
>>
>> Thanks,

1000 Cassandra Nodes running on Kubernetes 1.3

[David Aronchick]

Just thought I'd share this big milestone for all Cassandra users!

https://news.ycombinator.com/item?id=12089272

Open source equivalents of OpsCenter

[Kevin O'Connor]

Now that OpsCenter doesn't work with open source installs, are there any
runs at an open source equivalent? I'd be more interested in looking at
metrics of a running cluster and doing other tasks like managing
repairs/rolling restarts more so than historical data.

Re: NoHostAvailableException coming up on our server

[Abhinav Solan]

Thanks a lot for suggestion Romain, I have done the setup to see the driver
logs, but haven't seen that error again.
Also thanks for the MaxRequestPerConnection tip, I will change it to 32K.

Regards,
Abhinav

On Wed, Jul 13, 2016 at 1:02 PM Romain Hardouin  wrote:

> Put the driver logs in debug mode to see what's happen.
> Btw I am surprised by the few requests by connections in your setup:
>
> .setConnectionsPerHost(HostDistance.LOCAL, 20, 20)
>  .setMaxRequestsPerConnection(HostDistance.LOCAL, 128)
>
> It looks like a protocol v2 settings (Cassandra 2.0) because it was
> limited to 128 requests per connection. You're using C* 3.3 so the protocol
> v4.
> You can go up to 32K since protocol v3. As a first step I would try to
> open only 2 connections with 16K in MaxRequestsPerConnection. Then try to
> fine tune.
>
> Best,
>
> Romain
>
>
> Le Mardi 12 juillet 2016 23h57, Abhinav Solan  a
> écrit :
>
>
> I am using 3.0.0 version over apache-cassandra-3.3
>
> On Tue, Jul 12, 2016 at 2:37 PM Riccardo Ferrari 
> wrote:
>
> What driver version are you using?
>
> You can look at the LoggingRetryPolicy to have more meaningful messages in
> your logs.
>
> best,
>
> On Tue, Jul 12, 2016 at 9:02 PM, Abhinav Solan 
> wrote:
>
> Thanks, Johnny
> Actually, they were running .. it went through a series of read and writes
> .. and recovered after the error.
> Is there any settings I can specify in preparing the Session at java
> client driver level, here are my current settings -
>
> PoolingOptions poolingOptions = new PoolingOptions()
>  .setConnectionsPerHost(HostDistance.LOCAL, 20, 20)
>  .setMaxRequestsPerConnection(HostDistance.LOCAL, 128)
>  .setNewConnectionThreshold(HostDistance.LOCAL, 100);
>
>  Cluster.Builder builder = Cluster.builder()
>  .addContactPoints(cp)
>  .withPoolingOptions(poolingOptions)
>  .withProtocolVersion(ProtocolVersion.NEWEST_SUPPORTED)
>  .withPort(port);
>
>
>
> On Tue, Jul 12, 2016 at 11:47 AM Johnny Miller 
> wrote:
>
> Abhinav - your getting that as the driver isn’t finding any hosts up for
> your query. You probably need to check if all the nodes in your cluster are
> running.
>
> See:
> http://docs.datastax.com/en/drivers/java/3.0/com/datastax/driver/core/exceptions/NoHostAvailableException.html
>
>
> Johnny
>
> On 12 Jul 2016, at 18:46, Abhinav Solan  wrote:
>
> Hi Everyone,
>
> I am getting this error on our server, it comes and goes seems the
> connection drops a comes back after a while -
>
> Caused by: com.datastax.driver.core.exceptions.NoHostAvailableException: All 
> host(s) tried for query failed (tried: :9042 
> (com.datastax.driver.core.exceptions.ConnectionException: [] 
> Pool is CLOSING))
>   at 
> com.datastax.driver.core.RequestHandler.reportNoMoreHosts(RequestHandler.java:218)
>   at 
> com.datastax.driver.core.RequestHandler.access$1000(RequestHandler.java:43)
>   at 
> com.datastax.driver.core.RequestHandler$SpeculativeExecution.sendRequest(RequestHandler.java:284)
>   at 
> com.datastax.driver.core.RequestHandler.startNewExecution(RequestHandler.java:115)
>   at 
> com.datastax.driver.core.RequestHandler.sendRequest(RequestHandler.java:91)
>   at 
> com.datastax.driver.core.SessionManager.executeAsync(SessionManager.java:129)
>
> Can anyone suggest me what can be done to handle this error ?
>
>
> Thanks,
>
> Abhinav
>
>
>
>
>
>

Re: (C)* stable version after 3.5

[Alain RODRIGUEZ]

Hi Anuj

From
https://docs.datastax.com/en/latest-upgrade/upgrade/cassandra/upgrdBestPractCassandra.html
:


>- Employ a continual upgrade strategy for each year. Upgrades are
>impacted by the version you are upgrading from and the version you are
>upgrading to. The greater the gap between the current version and the
>target version, the more complex the upgrade.
>
>
And I could not find it but historically I am quite sure it was explicitly
recommended not to skip a major update (for a rolling upgrade), even if I
could not find it. Anyway it is clear that the bigger the gap is, the more
careful we need to be.

On the other hand, I see 2.2 as a 2.1 + some feature but no real breaking
changes (as 3.0 was already on the pipe) and doing a 2.2 was decided
because 3.0 was taking a long time to be released and some feature were
ready for a while.

I might be wrong on some stuff above, but one can only speak with his
knowledge and from his point of view. So I ended up saying:

Also I am not sure if the 2.2 major version is something you can skip while
> upgrading through a rolling restart. I believe you can, but it is not what
> is recommended.
>

Note that "I am not sure", "I believe you can"... So it was more a thought,
something to explore for Varun :-).

And I actually encouraged him to move forward. Now that Tyler Hobbs
confirmed it works, you can put a lot more trust on the fact that this
upgrade will work :-). I would still encourage people to test it (for
client compatibility, corner cases due to models, ...).

I hope I am more clear now,

C*heers,
---
Alain Rodriguez - al...@thelastpickle.com
France

The Last Pickle - Apache Cassandra Consulting
http://www.thelastpickle.com

2016-07-13 18:39 GMT+02:00 Tyler Hobbs :

>
> On Wed, Jul 13, 2016 at 11:32 AM, Anuj Wadehra 
> wrote:
>
>> Why do you think that skipping 2.2 is not recommended when NEWS.txt
>> suggests otherwise? Can you elaborate?
>
>
> We test upgrading from 2.1 -> 3.x and upgrading from 2.2 -> 3.x
> equivalently.  There should not be a difference in terms of how well the
> upgrade is supported.
>
>
> --
> Tyler Hobbs
> DataStax 
>

Re: Open source equivalents of OpsCenter

[Ranjib Dey]

we use datadog (metrics emitted as raw statsd) for the dashboard. All
repair & compaction is done via blender & serf[1].
[1]https://github.com/pagerduty/blender


On Wed, Jul 13, 2016 at 2:42 PM, Kevin O'Connor  wrote:

> Now that OpsCenter doesn't work with open source installs, are there any
> runs at an open source equivalent? I'd be more interested in looking at
> metrics of a running cluster and doing other tasks like managing
> repairs/rolling restarts more so than historical data.
>

Re: Is my cluster normal?

[Romain Hardouin]

Same behavior here with a very different setup.After an upgrade to 2.1.14 (from 
2.0.17) I see a high load and many NTR "all time blocked". Offheap memtable 
lowered the blocked NTR for me, I put a comment on CASSANDRA-11363 
Best,
Romain

Le Mercredi 13 juillet 2016 20h18, Yuan Fang  a 
écrit :
 

 Sometimes, the Pending can change from 128 to 129, 125 etc.

On Wed, Jul 13, 2016 at 10:32 AM, Yuan Fang  wrote:

$nodetool tpstats 
...Pool Name                               Active   Pending   Completed   
Blocked      All time blocked
Native-Transport-Requests       128       128        1420623949         1       
  142821509
...


What is this? Is it normal?
On Tue, Jul 12, 2016 at 3:03 PM, Yuan Fang  wrote:

Hi Jonathan,
Here is the result:
ubuntu@ip-172-31-44-250:~$ iostat -dmx 2 10Linux 3.13.0-74-generic 
(ip-172-31-44-250)  07/12/2016  _x86_64_ (4 CPU)
Device:         rrqm/s   wrqm/s     r/s     w/s    rMB/s    wMB/s avgrq-sz 
avgqu-sz   await r_await w_await  svctm  %utilxvda              0.01     2.13   
 0.74    1.55     0.01     0.02    27.77     0.00    0.74    0.89    0.66   
0.43   0.10xvdf              0.01     0.58  237.41   52.50    12.90     6.21   
135.02     2.32    8.01    3.65   27.72   0.57  16.63
Device:         rrqm/s   wrqm/s     r/s     w/s    rMB/s    wMB/s avgrq-sz 
avgqu-sz   await r_await w_await  svctm  %utilxvda              0.00     7.50   
 0.00    2.50     0.00     0.04    32.00     0.00    1.60    0.00    1.60   
1.60   0.40xvdf              0.00     0.00  353.50    0.00    24.12     0.00   
139.75     0.49    1.37    1.37    0.00   0.58  20.60
Device:         rrqm/s   wrqm/s     r/s     w/s    rMB/s    wMB/s avgrq-sz 
avgqu-sz   await r_await w_await  svctm  %utilxvda              0.00     0.00   
 0.00    1.00     0.00     0.00     8.00     0.00    0.00    0.00    0.00   
0.00   0.00xvdf              0.00     2.00  463.50   35.00    30.69     2.86   
137.84     0.88    1.77    1.29    8.17   0.60  30.00
Device:         rrqm/s   wrqm/s     r/s     w/s    rMB/s    wMB/s avgrq-sz 
avgqu-sz   await r_await w_await  svctm  %utilxvda              0.00     0.00   
 0.00    1.00     0.00     0.00     8.00     0.00    0.00    0.00    0.00   
0.00   0.00xvdf              0.00     0.00   99.50   36.00     8.54     4.40   
195.62     1.55    3.88    1.45   10.61   1.06  14.40
Device:         rrqm/s   wrqm/s     r/s     w/s    rMB/s    wMB/s avgrq-sz 
avgqu-sz   await r_await w_await  svctm  %utilxvda              0.00     5.00   
 0.00    1.50     0.00     0.03    34.67     0.00    1.33    0.00    1.33   
1.33   0.20xvdf              0.00     1.50  703.00  195.00    48.83    23.76   
165.57     6.49    8.36    1.66   32.51   0.55  49.80
Device:         rrqm/s   wrqm/s     r/s     w/s    rMB/s    wMB/s avgrq-sz 
avgqu-sz   await r_await w_await  svctm  %utilxvda              0.00     0.00   
 0.00    1.00     0.00     0.04    72.00     0.00    0.00    0.00    0.00   
0.00   0.00xvdf              0.00     2.50  149.50   69.50    10.12     6.68   
157.14     0.74    3.42    1.18    8.23   0.51  11.20
Device:         rrqm/s   wrqm/s     r/s     w/s    rMB/s    wMB/s avgrq-sz 
avgqu-sz   await r_await w_await  svctm  %utilxvda              0.00     5.00   
 0.00    2.50     0.00     0.03    24.00     0.00    0.00    0.00    0.00   
0.00   0.00xvdf              0.00     0.00   61.50   22.50     5.36     2.75   
197.64     0.33    3.93    1.50   10.58   0.88   7.40
Device:         rrqm/s   wrqm/s     r/s     w/s    rMB/s    wMB/s avgrq-sz 
avgqu-sz   await r_await w_await  svctm  %utilxvda              0.00     0.00   
 0.00    0.50     0.00     0.00     8.00     0.00    0.00    0.00    0.00   
0.00   0.00xvdf              0.00     0.00  375.00    0.00    24.84     0.00   
135.64     0.45    1.20    1.20    0.00   0.57  21.20
Device:         rrqm/s   wrqm/s     r/s     w/s    rMB/s    wMB/s avgrq-sz 
avgqu-sz   await r_await w_await  svctm  %utilxvda              0.00     1.00   
 0.00    6.00     0.00     0.03     9.33     0.00    0.00    0.00    0.00   
0.00   0.00xvdf              0.00     0.00  542.50   23.50    35.08     2.83   
137.16     0.80    1.41    1.15    7.23   0.49  28.00
Device:         rrqm/s   wrqm/s     r/s     w/s    rMB/s    wMB/s avgrq-sz 
avgqu-sz   await r_await w_await  svctm  %utilxvda              0.00     3.50   
 0.50    1.50     0.00     0.02    24.00     0.00    0.00    0.00    0.00   
0.00   0.00xvdf              0.00     1.50  272.00  153.50    16.18    18.67   
167.73    14.32   33.66    1.39   90.84   0.81  34.60


On Tue, Jul 12, 2016 at 12:34 PM, Jonathan Haddad  wrote:

When you have high system load it means your CPU is waiting for *something*, 
and in my experience it's usually slow disk.  A disk connected over network has 
been a culprit for me many times.
On Tue, Jul 12, 2016 at 12:33 PM Jonathan Haddad  wrote:

Can do you do:
iostat 

Re: CPU high load

[Romain Hardouin]

Did you upgrade from a previous version? DId you make some schema changes like 
compaction strategy, compression, bloom filter, etc.?What about the R/W 
requests?  SharedPool Workers are... shared ;-) Put logs in debug to see some 
examples of what services are using this pool (many actually).

Best,
Romain 

Le Mercredi 13 juillet 2016 18h15, Patrick McFadin  a 
écrit :
 

 Might be more clear looking at nodetool tpstats 
>From there you can see all the thread pools and if there are any blocks. Could 
>be something subtle like network. 
On Tue, Jul 12, 2016 at 3:23 PM, Aoi Kadoya  wrote:

Hi,

I am running 6 nodes vnode cluster with DSE 4.8.1, and since few weeks
ago, all of the cluster nodes are hitting avg. 15-20 cpu load.
These nodes are running on VMs(VMware vSphere) that have 8vcpu
(1core/socket)-16 vRAM.(JVM options : -Xms8G -Xmx8G -Xmn800M)

At first I thought this is because of CPU iowait, however, iowait is
constantly low(in fact it's 0 almost all time time), CPU steal time is
also 0%.

When I took a thread dump, I found some of "SharedPool-Worker" threads
are consuming CPU and those threads seem to be waiting for something
so I assume this is the cause of cpu load.

"SharedPool-Worker-1" #240 daemon prio=5 os_prio=0
tid=0x7fabf459e000 nid=0x39b3 waiting on condition
[0x7faad7f02000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:85)
at java.lang.Thread.run(Thread.java:745)

Thread dump looks like this, but I am not sure what is this
sharedpool-worker waiting for.
Would you please help me with the further trouble shooting?
I am also reading the thread posted by Yuan as the situation is very
similar to mine but I didn't get any blocked, dropped or pending count
in my tpstat result.

Thanks,
Aoi




  

Re: CPU high load

[Aoi Kadoya]

Hi Romain,

No, I don't think we upgraded cassandra version or changed any of
those schema elements. After I realized this high load issue, I found
that some of the tables have a shorter gc_grace_seconds(1day) than the
rest and because it seemed causing constant compaction cycles, I have
changed them to 10days. but again, that's after load hit this high
number.
some of nodes got eased a little bit after changing gc_grace_seconds
values and repairing nodes, but since few days ago, all of nodes are
constantly reporting load 15-20.

Thank you for the suggestion about logging, let me try to change the
log level to see what I can get from it.

Thanks,
Aoi


2016-07-13 13:28 GMT-07:00 Romain Hardouin :
> Did you upgrade from a previous version? DId you make some schema changes
> like compaction strategy, compression, bloom filter, etc.?
> What about the R/W requests?
> SharedPool Workers are... shared ;-) Put logs in debug to see some examples
> of what services are using this pool (many actually).
>
> Best,
>
> Romain
>
>
> Le Mercredi 13 juillet 2016 18h15, Patrick McFadin  a
> écrit :
>
>
> Might be more clear looking at nodetool tpstats
>
> From there you can see all the thread pools and if there are any blocks.
> Could be something subtle like network.
>
> On Tue, Jul 12, 2016 at 3:23 PM, Aoi Kadoya  wrote:
>
> Hi,
>
> I am running 6 nodes vnode cluster with DSE 4.8.1, and since few weeks
> ago, all of the cluster nodes are hitting avg. 15-20 cpu load.
> These nodes are running on VMs(VMware vSphere) that have 8vcpu
> (1core/socket)-16 vRAM.(JVM options : -Xms8G -Xmx8G -Xmn800M)
>
> At first I thought this is because of CPU iowait, however, iowait is
> constantly low(in fact it's 0 almost all time time), CPU steal time is
> also 0%.
>
> When I took a thread dump, I found some of "SharedPool-Worker" threads
> are consuming CPU and those threads seem to be waiting for something
> so I assume this is the cause of cpu load.
>
> "SharedPool-Worker-1" #240 daemon prio=5 os_prio=0
> tid=0x7fabf459e000 nid=0x39b3 waiting on condition
> [0x7faad7f02000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
> at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:85)
> at java.lang.Thread.run(Thread.java:745)
>
> Thread dump looks like this, but I am not sure what is this
> sharedpool-worker waiting for.
> Would you please help me with the further trouble shooting?
> I am also reading the thread posted by Yuan as the situation is very
> similar to mine but I didn't get any blocked, dropped or pending count
> in my tpstat result.
>
> Thanks,
> Aoi
>
>
>
>

Exclude a host from the repair process

[Jean Carlo]

If a node is down in my cluster.

Is it possible to exclude him from the repair process in order to continue
with the repair?
If not
Is the repair continue reparing the other replicas even if one is down?

Best regards

Jean Carlo

"The best way to predict the future is to invent it" Alan Kay

Re: how to start a embed cassandra instance?

[DuyHai Doan]

As for Achilles, no I start Cassandra in the same JVM. It is meant to be
used for testing purpose only. I also faced dependency issue with different
version of Guava so I excluded the Guava pulled by the Datastax Java driver
to use the one pulled by C* itself:
https://github.com/doanduyhai/Achilles/blob/master/achilles-embedded/pom.xml#L52-L55



On Wed, Jul 13, 2016 at 2:28 PM, Ken Hancock 
wrote:

> Do either cassandra-unit or Achilles fork Cassandra to a separate JVM?
> Guava libraries create a dependency hell with our current use of Hector's
> embedded server.  We're starting to migrate to the Datastax Java driver
> with yet another guava version.  I know Farsandra supports forking, so that
> was where I was thinking of going first.
>
>
>
>
> On Tue, Jul 12, 2016 at 9:37 AM, DuyHai Doan  wrote:
>
>> If you're looking something similar to cassandra-unit with Apache 2
>> licence, there is a module in Achilles project that provides the same
>> thing:
>> https://github.com/doanduyhai/Achilles/wiki/CQL-embedded-cassandra-server
>>
>> On Tue, Jul 12, 2016 at 12:56 PM, Peddi, Praveen 
>> wrote:
>>
>>> We do something similar by starting CassandraDaemon class directly (you
>>> would need to provide a yaml file though). You can start and stop
>>> CassandraDaemon class from your unit test (typically @BeforeClass).
>>>
>>> Praveen
>>>
>>> On Jul 12, 2016, at 3:30 AM, Stone Fang  wrote:
>>>
>>> Hi,
>>> how to start a embed cassandra instance?so we can do a unit test on
>>> local,dont need to start a
>>> cassandra server.
>>>
>>> https://github.com/jsevellec/cassandra-unit this project is good,but
>>> the license is not suitable.
>>> how do you achieve this?
>>>
>>> thanks in advance
>>>
>>> stone
>>>
>>>
>>
>
>
> --
> *Ken Hancock *| System Architect, Advanced Advertising
> SeaChange International
> 50 Nagog Park
> Acton, Massachusetts 01720
> ken.hanc...@schange.com | www.schange.com | NASDAQ:SEAC
> 
> Office: +1 (978) 889-3329 | [image: Google Talk:] ken.hanc...@schange.com
>  | [image: Skype:]hancockks | [image: Yahoo IM:]hancockks [image:
> LinkedIn] 
>
> [image: SeaChange International]
> 
> This e-mail and any attachments may contain information which is SeaChange
> International confidential. The information enclosed is intended only for
> the addressees herein and may not be copied or forwarded without permission
> from SeaChange International.
>

Re: how to start a embed cassandra instance?

[Ken Hancock]

Do either cassandra-unit or Achilles fork Cassandra to a separate JVM?
Guava libraries create a dependency hell with our current use of Hector's
embedded server.  We're starting to migrate to the Datastax Java driver
with yet another guava version.  I know Farsandra supports forking, so that
was where I was thinking of going first.




On Tue, Jul 12, 2016 at 9:37 AM, DuyHai Doan  wrote:

> If you're looking something similar to cassandra-unit with Apache 2
> licence, there is a module in Achilles project that provides the same
> thing:
> https://github.com/doanduyhai/Achilles/wiki/CQL-embedded-cassandra-server
>
> On Tue, Jul 12, 2016 at 12:56 PM, Peddi, Praveen  wrote:
>
>> We do something similar by starting CassandraDaemon class directly (you
>> would need to provide a yaml file though). You can start and stop
>> CassandraDaemon class from your unit test (typically @BeforeClass).
>>
>> Praveen
>>
>> On Jul 12, 2016, at 3:30 AM, Stone Fang  wrote:
>>
>> Hi,
>> how to start a embed cassandra instance?so we can do a unit test on
>> local,dont need to start a
>> cassandra server.
>>
>> https://github.com/jsevellec/cassandra-unit this project is good,but the
>> license is not suitable.
>> how do you achieve this?
>>
>> thanks in advance
>>
>> stone
>>
>>
>


-- 
*Ken Hancock *| System Architect, Advanced Advertising
SeaChange International
50 Nagog Park
Acton, Massachusetts 01720
ken.hanc...@schange.com | www.schange.com | NASDAQ:SEAC

Office: +1 (978) 889-3329 | [image: Google Talk:]
ken.hanc...@schange.com | [image:
Skype:]hancockks | [image: Yahoo IM:]hancockks [image: LinkedIn]


[image: SeaChange International]

This e-mail and any attachments may contain information which is SeaChange
International confidential. The information enclosed is intended only for
the addressees herein and may not be copied or forwarded without permission
from SeaChange International.