Data Model for One To Many - Itemcontainer - Items

[malte]

hi,

i have two CFs "ItemContainer" and "Items".

I used to have a secondary index in "Items" referring to the  
"Itemcontainer". Something like:


CREATE table items (key uuid primary key, container uuid, slot int 
CREATE INDEX items_container ON items(container)

i change the "container" cell quite often when changing the  
itemcontainer. Documentation says that a secondary index shouldnt be  
used in this case.


So i tried something like:

 primary key(container, key)

in items. now i can query all items for an itemcontainer just fine.  
but how do i put the item in another itemcontainer? you cant override  
parts of the primary key. so do i really have to delete the item and  
reinsert all the date with a different "container" field?


Doesn't this create a lot of tombstones? Also "Items" has like 20  
columns with maps and lists and everything...


any ideas?


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: apache-cassandra 2.2.8 rpm

[Michael Shuler]

There is no Apache Cassandra RPM for 2.2.8. If there were, it would be 
basically identical to the Datastax package anyway. The differences 
would be package name and a dependency on python 2.7 in the spec for 
Apache Cassandra. (I used to maintain the Datastax Community packages 
and currently build the Apache Cassandra ones)


The Apache Cassandra project started building RPMS with version 2.2.10 
in the 2.2 series. The RPM packages pick up where Datastax left off 
(although a version or two may have been missed). If you need to stay on 
2.2.8, just use the one you're running now, it's fine.


My suggestion would be the same, if you are planning on upgrading anyway 
- install the latest 2.2 series RPM package, which is currently 2.2.12, 
and follow the NEWS.txt notes as with any upgrade.


Very large warning: test your upgrade on dev/staging cluster. Back up 
configs/data, set up Apache Cassandra RPM repo config, drop the Datastax 
one, and upgrade to latest in your series. The myriad of possible 
package name conflicts were not added to the Apache Cassandra RPMs, so 
upgrade with care - the Apache Cassandra package is not going to 
automagically remove the old community packages, so you'd need to do the 
removal yourself.


Hope that helps!

--
Kind regards,
Michael


On 06/05/2018 10:00 AM, ukevg...@gmail.com wrote:



On 2018/06/05 14:56:24, Carlos Rolo  wrote:

I would recommend migrate to a higher version of Apache Cassandra. Since
Datastax always push some extra patches in their distribution. So I would
go 2.2.8 -> 2.2.9+ at least. Since it's a minor upgrade I would read this
https://github.com/apache/cassandra/blob/cassandra-2.2/NEWS.txt and upgrade
to the 2.2.12.

[image: Pythian]
*Carlos Rolo* | Open Source Consultant | [image: LinkedIn]

*m* +351 918 918 100
r...@pythian.com   *www.pythian.com*

[image: Pythian]


On Tue, Jun 5, 2018 at 3:49 PM, ukevg...@gmail.com 
wrote:




On 2018/06/05 14:28:20, Nicolas Guyomar 
wrote:

Hi,

I believe this rpm was built by Datastax right ?
https://rpm.datastax.com/community/noarch/ is what you seem to be

looking

for
Otherwise newest rpm are here :
https://www.apache.org/dist/cassandra/redhat/22x/

On 5 June 2018 at 16:21, ukevg...@gmail.com  wrote:


Hi everybody,

I am not able to find an RPM package for apache-cassandra 2.2.8

Is there anyone who can share a link I really couldn't find it.

Thank you

Ev

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org



I am trying to migrate from Datastax to apache cassandra.
I already have datastax 2.2.8 installed just trying to migrate to Apache
cassandra 2.2.8

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org




--


--






I will do that if I can't find 2.2.8
Anybody who has apache-cassandra 2.2.8 will save me 3 months ?

Thank you,

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org




-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Repair slow, "Percent repaired" never updated

[Martin Mačura]

Hi,
we're on cassandra 3.11.2, and we're having some issues with repairs.
They take ages to complete, and some time ago the incremental repair
stopped working - that is, SSTables are not being marked as repaired,
even though the repair reports success.

Running a full or incremental repair does not make any difference.

Here's a log of a typical repair (omitted a lot of 'Maximum memory
usage' messages):

INFO  [Repair-Task-12] 2018-06-04 06:29:50,396 RepairRunnable.java:139
- Starting repair command #11 (af1aefc0-67c0-11e8-b07c-c365701888e8),
repairing keyspace prod with repair options (parallelism: parallel,
primary range: false, incremental: true, job threads: 1,
ColumnFamilies: [event], dataCenters: [DC1], hosts: [], # of ranges:
1280, pull repair: false)
INFO  [Repair-Task-12] 2018-06-04 06:29:51,497 RepairSession.java:228
- [repair #afc2ef90-67c0-11e8-b07c-c365701888e8] new session: will
sync /14.0.53.234, /14.0.52.115 on range [...] for asm_log.[event]
INFO  [Repair#11:1] 2018-06-04 06:29:51,776 RepairJob.java:169 -
[repair #afc2ef90-67c0-11e8-b07c-c365701888e8] Requesting merkle trees
for event (to [/14.0.52.115, /14.0.53.234])
INFO  [ValidationExecutor:10] 2018-06-04 06:31:13,859
NoSpamLogger.java:91 - Maximum memory usage reached (512.000MiB),
cannot allocate chunk of 1.000MiB
WARN  [PERIODIC-COMMIT-LOG-SYNCER] 2018-06-04 06:32:01,385
NoSpamLogger.java:94 - Out of 14 commit log syncs over the past
134.02s with average duration of 34.90ms, 2 have exceeded the
configured commit interval by an average of 60.66ms
...
INFO  [ValidationExecutor:10] 2018-06-04 13:31:19,011
NoSpamLogger.java:91 - Maximum memory usage reached (512.000MiB),
cannot allocate chunk of 1.000MiB
INFO  [AntiEntropyStage:1] 2018-06-04 13:37:17,357
RepairSession.java:180 - [repair
#afc2ef90-67c0-11e8-b07c-c365701888e8] Received merkle tree for event
from /14.0.52.115
INFO  [ValidationExecutor:10] 2018-06-04 13:46:19,281
NoSpamLogger.java:91 - Maximum memory usage reached (512.000MiB),
cannot allocate chunk of 1.000MiB
INFO  [IndexSummaryManager:1] 2018-06-04 13:57:18,772
IndexSummaryRedistribution.java:76 - Redistributing index summaries
INFO  [AntiEntropyStage:1] 2018-06-04 13:58:21,971
RepairSession.java:180 - [repair
#afc2ef90-67c0-11e8-b07c-c365701888e8] Received merkle tree for event
from /14.0.53.234
INFO  [RepairJobTask:4] 2018-06-04 13:58:39,780 SyncTask.java:73 -
[repair #afc2ef90-67c0-11e8-b07c-c365701888e8] Endpoints /14.0.52.115
and /14.0.53.234 have 15406 range(s) out of sync for event
INFO  [RepairJobTask:4] 2018-06-04 13:58:39,781 LocalSyncTask.java:71
- [repair #afc2ef90-67c0-11e8-b07c-c365701888e8] Performing streaming
repair of 15406 ranges with /14.0.52.115
INFO  [RepairJobTask:4] 2018-06-04 13:59:49,075
StreamResultFuture.java:90 - [Stream
#6244fd50-67ff-11e8-b07c-c365701888e8] Executing streaming plan for
Repair
INFO  [StreamConnectionEstablisher:3] 2018-06-04 13:59:49,076
StreamSession.java:266 - [Stream
#6244fd50-67ff-11e8-b07c-c365701888e8] Starting streaming to
/14.0.52.115
INFO  [StreamConnectionEstablisher:3] 2018-06-04 13:59:49,089
StreamCoordinator.java:264 - [Stream
#6244fd50-67ff-11e8-b07c-c365701888e8, ID#0] Beginning stream session
with /14.0.52.115
INFO  [STREAM-IN-/14.0.52.115:7000] 2018-06-04 14:01:14,423
StreamResultFuture.java:173 - [Stream
#6244fd50-67ff-11e8-b07c-c365701888e8 ID#0] Prepare completed.
Receiving 321 files(6.238GiB), sending 318 files(6.209GiB)
WARN  [Service Thread] 2018-06-04 14:12:15,578 GCInspector.java:282 -
ConcurrentMarkSweep GC in 4095ms.  CMS Old Gen: 4086661264 ->
1107272664; Par Eden Space: 503316480 -> 0; Par Survivor Space:
21541464 -> 0
...
WARN  [GossipTasks:1] 2018-06-04 14:12:15,677 FailureDetector.java:288
- Not marking nodes down due to local pause of 5123793157 > 50
INFO  [ScheduledTasks:1] 2018-06-04 14:12:20,611 NoSpamLogger.java:91
- Some operations were slow, details available at debug level
(debug.log)
INFO  [STREAM-IN-/14.0.52.115:7000] 2018-06-04 14:14:29,188
StreamResultFuture.java:187 - [Stream
#6244fd50-67ff-11e8-b07c-c365701888e8] Session with /14.0.52.115 is
complete
INFO  [STREAM-IN-/14.0.52.115:7000] 2018-06-04 14:14:29,190
StreamResultFuture.java:219 - [Stream
#6244fd50-67ff-11e8-b07c-c365701888e8] All sessions completed
INFO  [STREAM-IN-/14.0.52.115:7000] 2018-06-04 14:14:29,190
LocalSyncTask.java:121 - [repair
#afc2ef90-67c0-11e8-b07c-c365701888e8] Sync complete using session
afc2ef90-67c0-11e8-b07c-c365701888e8 between /14.0.52.115 and
/14.0.53.234 on event
INFO  [RepairJobTask:5] 2018-06-04 14:14:29,191 RepairJob.java:143 -
[repair #afc2ef90-67c0-11e8-b07c-c365701888e8] event is fully synced
INFO  [RepairJobTask:5] 2018-06-04 14:14:29,193 RepairSession.java:270
- [repair #afc2ef90-67c0-11e8-b07c-c365701888e8] Session completed
successfully



Tablestats:
   SSTable count: 714
   Space used (live): 489416489322
   Space used (total): 489416489322
   Space used by snapshots (total): 0
  

Re: apache-cassandra 2.2.8 rpm

[ukevgeni]

On 2018/06/05 14:56:24, Carlos Rolo  wrote: 
> I would recommend migrate to a higher version of Apache Cassandra. Since
> Datastax always push some extra patches in their distribution. So I would
> go 2.2.8 -> 2.2.9+ at least. Since it's a minor upgrade I would read this
> https://github.com/apache/cassandra/blob/cassandra-2.2/NEWS.txt and upgrade
> to the 2.2.12.
> 
> [image: Pythian]
> *Carlos Rolo* | Open Source Consultant | [image: LinkedIn]
> 
> *m* +351 918 918 100
> r...@pythian.com   *www.pythian.com*
> 
> [image: Pythian]
> 
> 
> On Tue, Jun 5, 2018 at 3:49 PM, ukevg...@gmail.com 
> wrote:
> 
> >
> >
> > On 2018/06/05 14:28:20, Nicolas Guyomar 
> > wrote:
> > > Hi,
> > >
> > > I believe this rpm was built by Datastax right ?
> > > https://rpm.datastax.com/community/noarch/ is what you seem to be
> > looking
> > > for
> > > Otherwise newest rpm are here :
> > > https://www.apache.org/dist/cassandra/redhat/22x/
> > >
> > > On 5 June 2018 at 16:21, ukevg...@gmail.com  wrote:
> > >
> > > > Hi everybody,
> > > >
> > > > I am not able to find an RPM package for apache-cassandra 2.2.8
> > > >
> > > > Is there anyone who can share a link I really couldn't find it.
> > > >
> > > > Thank you
> > > >
> > > > Ev
> > > >
> > > > -
> > > > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> > > > For additional commands, e-mail: user-h...@cassandra.apache.org
> > > >
> > > >
> > I am trying to migrate from Datastax to apache cassandra.
> > I already have datastax 2.2.8 installed just trying to migrate to Apache
> > cassandra 2.2.8
> >
> > -
> > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: user-h...@cassandra.apache.org
> >
> >
> 
> -- 
> 
> 
> --
> 
> 
> 
> 
> 
I will do that if I can't find 2.2.8
Anybody who has apache-cassandra 2.2.8 will save me 3 months ?

Thank you,

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: apache-cassandra 2.2.8 rpm

[Carlos Rolo]

I would recommend migrate to a higher version of Apache Cassandra. Since
Datastax always push some extra patches in their distribution. So I would
go 2.2.8 -> 2.2.9+ at least. Since it's a minor upgrade I would read this
https://github.com/apache/cassandra/blob/cassandra-2.2/NEWS.txt and upgrade
to the 2.2.12.

[image: Pythian]
*Carlos Rolo* | Open Source Consultant | [image: LinkedIn]

*m* +351 918 918 100
r...@pythian.com   *www.pythian.com*

[image: Pythian]


On Tue, Jun 5, 2018 at 3:49 PM, ukevg...@gmail.com 
wrote:

>
>
> On 2018/06/05 14:28:20, Nicolas Guyomar 
> wrote:
> > Hi,
> >
> > I believe this rpm was built by Datastax right ?
> > https://rpm.datastax.com/community/noarch/ is what you seem to be
> looking
> > for
> > Otherwise newest rpm are here :
> > https://www.apache.org/dist/cassandra/redhat/22x/
> >
> > On 5 June 2018 at 16:21, ukevg...@gmail.com  wrote:
> >
> > > Hi everybody,
> > >
> > > I am not able to find an RPM package for apache-cassandra 2.2.8
> > >
> > > Is there anyone who can share a link I really couldn't find it.
> > >
> > > Thank you
> > >
> > > Ev
> > >
> > > -
> > > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> > > For additional commands, e-mail: user-h...@cassandra.apache.org
> > >
> > >
> I am trying to migrate from Datastax to apache cassandra.
> I already have datastax 2.2.8 installed just trying to migrate to Apache
> cassandra 2.2.8
>
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
>
>

-- 


--

Re: apache-cassandra 2.2.8 rpm

[ukevgeni]

On 2018/06/05 14:28:20, Nicolas Guyomar  wrote: 
> Hi,
> 
> I believe this rpm was built by Datastax right ?
> https://rpm.datastax.com/community/noarch/ is what you seem to be looking
> for
> Otherwise newest rpm are here :
> https://www.apache.org/dist/cassandra/redhat/22x/
> 
> On 5 June 2018 at 16:21, ukevg...@gmail.com  wrote:
> 
> > Hi everybody,
> >
> > I am not able to find an RPM package for apache-cassandra 2.2.8
> >
> > Is there anyone who can share a link I really couldn't find it.
> >
> > Thank you
> >
> > Ev
> >
> > -
> > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: user-h...@cassandra.apache.org
> >
> >
I am trying to migrate from Datastax to apache cassandra.
I already have datastax 2.2.8 installed just trying to migrate to Apache 
cassandra 2.2.8

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Log application Queries

[Luigi Tagliamonte]

I implemented an audit query handler that archives the queries in ES here:
https://github.com/ltagliamonte/cassandra-audit
PRs are welcome!

On Mon, May 28, 2018 at 1:55 AM, Horia Mocioi 
wrote:

> Hello,
>
> Another way to do it would be to create your own QueryHandler:
>
>- create a class that would implement the QueryHandler interface and
>make Cassandra aware of it
>- in that class you can maintain a list of the queries (add to this
>list when prepare method is being called) and the current query that
>you will get from the list when getPrepared it's called; you can get
>it from the list using the MD5Digest id
>- when processPrepared is called you can replace the ? in the query
>string with the values in the QueryOptions options.getValues().
>
>
> On fre, 2018-05-25 at 11:24 -0400, Nitan Kainth wrote:
>
> Hi,
>
> I would like to log all C* queries hitting cluster. Could someone please
> tell me how can I do it at cluster level?
> Will nodetool setlogginglevel work? If so, please share example with
> library name.
>
> C* version 3.11
>
>

Re: apache-cassandra 2.2.8 rpm

[Nicolas Guyomar]

Hi,

I believe this rpm was built by Datastax right ?
https://rpm.datastax.com/community/noarch/ is what you seem to be looking
for
Otherwise newest rpm are here :
https://www.apache.org/dist/cassandra/redhat/22x/

On 5 June 2018 at 16:21, ukevg...@gmail.com  wrote:

> Hi everybody,
>
> I am not able to find an RPM package for apache-cassandra 2.2.8
>
> Is there anyone who can share a link I really couldn't find it.
>
> Thank you
>
> Ev
>
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
>
>

apache-cassandra 2.2.8 rpm

[ukevgeni]

Hi everybody,

I am not able to find an RPM package for apache-cassandra 2.2.8

Is there anyone who can share a link I really couldn't find it.

Thank you

Ev

-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Single Host: Fix "Unknown CF" issue

[mm]

Hello Evelyn,

if we do what you say cassandra creates a new, empty column family 
directory on restart and the stops with the same exception.


One point i forgot to mention is that we've still got data in the commit 
log. (99.9% for other keyspaces).
Are there any tools which we can use to examine the sstable or the 
commitlog files to dig further into this issue?


Or:
Can we setup a new cassandra installation and copy the data of the other 
keyspacs to the new instance?


The column family which shows this error does not contain important 
data. We're just very uncertain now what to do if this happens with 
important data.
(ok - maybe this problem is not that important if we use a cluster of 
e.g. 3 nodes and a replication factor of 2 - but it leaves a strange 
impression about cassandra anyway).


greetings,
Michael


On 05.06.2018 15:31, Evelyn Smith wrote:

Hey Michael,

I have a hunch.

If the system doesn’t recognise the column family which is stopping
the node from starting perhaps try copying the column family directory
to a backup then deleting it.

Then restart Cassandra. If it starts I’ll assume the schema didn’t
have the column family:
* Create the column family again (be careful to create it exactly how
it was in the original schema);
* Stop Cassandra again;
* Move the SSTables from the column family backup into the new column
family folder (you have to do this as the column family folder will
have a UUID in it’s name that will have changed); and
* Restart Cassandra.
You should now have Cassandra running without losing your data.

If Cassandra doesn’t restart after deleting the column family
directory then just restore it from the backup and you are back to
square one.

Regards,
Evelyn.


On 5 Jun 2018, at 7:32 pm, m...@vis.at wrote:

Hi all!

We're using cassandra since a couple of month to get familiar with it. 
We're currently using only 1-node. Yesterday our server had to be 
restarted and now cassandra does not start anymore.


It reports:
INFO  [main] 2018-06-05 09:50:43,030 ColumnFamilyStore.java:406 - 
Initializing system_schema.indexes
INFO  [main] 2018-06-05 09:50:43,036 ViewManager.java:137 - Not 
submitting build tasks for views in keyspace system_schema as storage 
service is not initialized
INFO  [main] 2018-06-05 09:50:43,283 ColumnFamilyStore.java:406 - 
Initializing system_traces.events
INFO  [main] 2018-06-05 09:50:43,286 ColumnFamilyStore.java:406 - 
Initializing system_traces.sessions
INFO  [main] 2018-06-05 09:50:43,287 ViewManager.java:137 - Not 
submitting build tasks for views in keyspace system_traces as storage 
service is not initialized
INFO  [main] 2018-06-05 09:50:43,300 ColumnFamilyStore.java:406 - 
Initializing m2m_auth.user
INFO  [main] 2018-06-05 09:50:43,302 ColumnFamilyStore.java:406 - 
Initializing m2m_auth.eventsbytag1
INFO  [main] 2018-06-05 09:50:43,306 ColumnFamilyStore.java:406 - 
Initializing m2m_auth.mail2user
ERROR [main] 2018-06-05 09:50:43,311 CassandraDaemon.java:706 - 
Exception encountered during startup
java.lang.IllegalArgumentException: Unknown CF 
0f6c8b36-5f34-11e8-a476-c93745f84272
   at 
org.apache.cassandra.db.Keyspace.getColumnFamilyStore(Keyspace.java:204) 
~[apache-cassandra-3.11.0.jar:3.11.0]
   at 
org.apache.cassandra.db.view.ViewManager.addView(ViewManager.java:152) 
~[apache-cassandra-3.11.0.jar:3.11.0]
   at 
org.apache.cassandra.db.view.ViewManager.reload(ViewManager.java:125) 
~[apache-cassandra-3.11.0.jar:3.11.0]
   at org.apache.cassandra.db.Keyspace.(Keyspace.java:324) 
~[apache-cassandra-3.11.0.jar:3.11.0]
   at org.apache.cassandra.db.Keyspace.open(Keyspace.java:127) 
~[apache-cassandra-3.11.0.jar:3.11.0]
   at org.apache.cassandra.db.Keyspace.open(Keyspace.java:104) 
~[apache-cassandra-3.11.0.jar:3.11.0]
   at 
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:292) 
[apache-cassandra-3.11.0.jar:3.11.0]
   at 
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:600) 
[apache-cassandra-3.11.0.jar:3.11.0]
   at 
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:689) 
[apache-cassandra-3.11.0.jar:3.11.0]


We do not know how to bring it up again and e.g. stackoverflow only 
recommends to delete the node and let it rebuild (which we cannot do 
as we've only 1 node currently).

Can anybody drop us a hint ?

What can we do if our node does not start?

We've found an entry in the data directory with the given UUID but at 
the time when we restarted the node the whole keyspace was idle for a 
couple of hours.
With the problem we're now _very_ concerned about data safety when we 
read that it can be a problem if e.g. tables are 
created/deleted/updated concurrently. But in our case we did not 
create/update tables concurrently and got this problem anyway


Thanks for any help!

greetings,
Michael



-
To unsubscribe, e-mail: 

How to identify which table causing Maximum Memory usage limit

[learner dba]

Hi,
We see this message often, cluster has multiple keyspaces and column families; 
How do I know which CF is causing this? Or it could be something else?Do we 
need to worry about this message?

INFO  [CounterMutationStage-1] 2018-06-05 13:36:35,983 NoSpamLogger.java:91 - 
Maximum memory usage reached (512.000MiB), cannot allocate chunk of 1.000MiB

Re: Single Host: Fix "Unknown CF" issue

[Evelyn Smith]

Hey Michael,

I have a hunch.

If the system doesn’t recognise the column family which is stopping the node 
from starting perhaps try copying the column family directory to a backup then 
deleting it.

Then restart Cassandra. If it starts I’ll assume the schema didn’t have the 
column family:
* Create the column family again (be careful to create it exactly how it was in 
the original schema);
* Stop Cassandra again;
* Move the SSTables from the column family backup into the new column family 
folder (you have to do this as the column family folder will have a UUID in 
it’s name that will have changed); and
* Restart Cassandra.
You should now have Cassandra running without losing your data.

If Cassandra doesn’t restart after deleting the column family directory then 
just restore it from the backup and you are back to square one.

Regards,
Evelyn.

> On 5 Jun 2018, at 7:32 pm, m...@vis.at wrote:
> 
> Hi all!
> 
> We're using cassandra since a couple of month to get familiar with it. We're 
> currently using only 1-node. Yesterday our server had to be restarted and now 
> cassandra does not start anymore.
> 
> It reports:
> INFO  [main] 2018-06-05 09:50:43,030 ColumnFamilyStore.java:406 - 
> Initializing system_schema.indexes
> INFO  [main] 2018-06-05 09:50:43,036 ViewManager.java:137 - Not submitting 
> build tasks for views in keyspace system_schema as storage service is not 
> initialized
> INFO  [main] 2018-06-05 09:50:43,283 ColumnFamilyStore.java:406 - 
> Initializing system_traces.events
> INFO  [main] 2018-06-05 09:50:43,286 ColumnFamilyStore.java:406 - 
> Initializing system_traces.sessions
> INFO  [main] 2018-06-05 09:50:43,287 ViewManager.java:137 - Not submitting 
> build tasks for views in keyspace system_traces as storage service is not 
> initialized
> INFO  [main] 2018-06-05 09:50:43,300 ColumnFamilyStore.java:406 - 
> Initializing m2m_auth.user
> INFO  [main] 2018-06-05 09:50:43,302 ColumnFamilyStore.java:406 - 
> Initializing m2m_auth.eventsbytag1
> INFO  [main] 2018-06-05 09:50:43,306 ColumnFamilyStore.java:406 - 
> Initializing m2m_auth.mail2user
> ERROR [main] 2018-06-05 09:50:43,311 CassandraDaemon.java:706 - Exception 
> encountered during startup
> java.lang.IllegalArgumentException: Unknown CF 
> 0f6c8b36-5f34-11e8-a476-c93745f84272
>at 
> org.apache.cassandra.db.Keyspace.getColumnFamilyStore(Keyspace.java:204) 
> ~[apache-cassandra-3.11.0.jar:3.11.0]
>at 
> org.apache.cassandra.db.view.ViewManager.addView(ViewManager.java:152) 
> ~[apache-cassandra-3.11.0.jar:3.11.0]
>at 
> org.apache.cassandra.db.view.ViewManager.reload(ViewManager.java:125) 
> ~[apache-cassandra-3.11.0.jar:3.11.0]
>at org.apache.cassandra.db.Keyspace.(Keyspace.java:324) 
> ~[apache-cassandra-3.11.0.jar:3.11.0]
>at org.apache.cassandra.db.Keyspace.open(Keyspace.java:127) 
> ~[apache-cassandra-3.11.0.jar:3.11.0]
>at org.apache.cassandra.db.Keyspace.open(Keyspace.java:104) 
> ~[apache-cassandra-3.11.0.jar:3.11.0]
>at 
> org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:292) 
> [apache-cassandra-3.11.0.jar:3.11.0]
>at 
> org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:600)
>  [apache-cassandra-3.11.0.jar:3.11.0]
>at 
> org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:689) 
> [apache-cassandra-3.11.0.jar:3.11.0]
> 
> We do not know how to bring it up again and e.g. stackoverflow only 
> recommends to delete the node and let it rebuild (which we cannot do as we've 
> only 1 node currently).
> Can anybody drop us a hint ?
> 
> What can we do if our node does not start?
> 
> We've found an entry in the data directory with the given UUID but at the 
> time when we restarted the node the whole keyspace was idle for a couple of 
> hours.
> With the problem we're now _very_ concerned about data safety when we read 
> that it can be a problem if e.g. tables are created/deleted/updated 
> concurrently. But in our case we did not create/update tables concurrently 
> and got this problem anyway
> 
> Thanks for any help!
> 
> greetings,
> Michael
> 
> 
> 
> -
> To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: user-h...@cassandra.apache.org
> 


-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Single Host: Fix "Unknown CF" issue

[mm]

Hi all!

We're using cassandra since a couple of month to get familiar with it. 
We're currently using only 1-node. Yesterday our server had to be 
restarted and now cassandra does not start anymore.


It reports:
INFO  [main] 2018-06-05 09:50:43,030 ColumnFamilyStore.java:406 - 
Initializing system_schema.indexes
INFO  [main] 2018-06-05 09:50:43,036 ViewManager.java:137 - Not 
submitting build tasks for views in keyspace system_schema as storage 
service is not initialized
INFO  [main] 2018-06-05 09:50:43,283 ColumnFamilyStore.java:406 - 
Initializing system_traces.events
INFO  [main] 2018-06-05 09:50:43,286 ColumnFamilyStore.java:406 - 
Initializing system_traces.sessions
INFO  [main] 2018-06-05 09:50:43,287 ViewManager.java:137 - Not 
submitting build tasks for views in keyspace system_traces as storage 
service is not initialized
INFO  [main] 2018-06-05 09:50:43,300 ColumnFamilyStore.java:406 - 
Initializing m2m_auth.user
INFO  [main] 2018-06-05 09:50:43,302 ColumnFamilyStore.java:406 - 
Initializing m2m_auth.eventsbytag1
INFO  [main] 2018-06-05 09:50:43,306 ColumnFamilyStore.java:406 - 
Initializing m2m_auth.mail2user
ERROR [main] 2018-06-05 09:50:43,311 CassandraDaemon.java:706 - 
Exception encountered during startup
java.lang.IllegalArgumentException: Unknown CF 
0f6c8b36-5f34-11e8-a476-c93745f84272
at 
org.apache.cassandra.db.Keyspace.getColumnFamilyStore(Keyspace.java:204) 
~[apache-cassandra-3.11.0.jar:3.11.0]
at 
org.apache.cassandra.db.view.ViewManager.addView(ViewManager.java:152) 
~[apache-cassandra-3.11.0.jar:3.11.0]
at 
org.apache.cassandra.db.view.ViewManager.reload(ViewManager.java:125) 
~[apache-cassandra-3.11.0.jar:3.11.0]
at org.apache.cassandra.db.Keyspace.(Keyspace.java:324) 
~[apache-cassandra-3.11.0.jar:3.11.0]
at org.apache.cassandra.db.Keyspace.open(Keyspace.java:127) 
~[apache-cassandra-3.11.0.jar:3.11.0]
at org.apache.cassandra.db.Keyspace.open(Keyspace.java:104) 
~[apache-cassandra-3.11.0.jar:3.11.0]
at 
org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:292) 
[apache-cassandra-3.11.0.jar:3.11.0]
at 
org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:600) 
[apache-cassandra-3.11.0.jar:3.11.0]
at 
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:689) 
[apache-cassandra-3.11.0.jar:3.11.0]


We do not know how to bring it up again and e.g. stackoverflow only 
recommends to delete the node and let it rebuild (which we cannot do as 
we've only 1 node currently).

Can anybody drop us a hint ?

What can we do if our node does not start?

We've found an entry in the data directory with the given UUID but at 
the time when we restarted the node the whole keyspace was idle for a 
couple of hours.
With the problem we're now _very_ concerned about data safety when we 
read that it can be a problem if e.g. tables are created/deleted/updated 
concurrently. But in our case we did not create/update tables 
concurrently and got this problem anyway


Thanks for any help!

greetings,
Michael



-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org

Re: Compaction throughput vs. number of compaction threads?

[Alexander Dejanovski]

Hi,

The compaction throughput is indeed shared by all compactors.
I would not advise to go below 8MB/s per compactor as slowing down
compactions put more pressure on the heap.

When tuning compaction, the first thing to do is evaluate the maximum
throughput your disks can sustain without impacting p99 read latencies.
Then you can consider raising the number of compactors if you're still
seeing contention.

So the advice would be : don't raise the number of compactors, 4 is
probably enough already and tune the compaction throughput if you're
running on SSDs or if you have an array of HDDs.

Cheers,

On Tue, Jun 5, 2018 at 10:48 AM Steinmaurer, Thomas <
thomas.steinmau...@dynatrace.com> wrote:

> Hello,
>
>
>
> most likely obvious and perhaps already answered in the past, but just
> want to be sure …
>
>
>
> E.g. I have set:
>
> concurrent_compactors: 4
>
> compaction_throughput_mb_per_sec: 16
>
>
>
> I guess this will lead to ~ 4MB/s per Thread if I have 4 compactions
> running in parallel?
>
>
>
> So, in case of upscaling a machine and following the recommendation in
> cassandra.yaml I may set:
>
>
>
> concurrent_compactors: 8
>
>
>
>
>
> If this throughput remains unchanged, does this mean that we have 2 MB/s
> per Thread then, e.g. largish compactions running on a single thread taking
> twice the time then?
>
>
>
> Using Cassandra 2.1 and 3.11 in case this matters.
>
>
>
>
>
> Thanks a lot!
>
> Thomas
>
>
> The contents of this e-mail are intended for the named addressee only. It
> contains information that may be confidential. Unless you are the named
> addressee or an authorized designee, you may not copy or use it, or
> disclose it to anyone else. If you received it in error please notify us
> immediately and then destroy it. Dynatrace Austria GmbH (registration
> number FN 91482h) is a company registered in Linz whose registered office
> is at 4040 Linz, Austria, Freistädterstraße 313
>
-- 
-
Alexander Dejanovski
France
@alexanderdeja

Consultant
Apache Cassandra Consulting
http://www.thelastpickle.com

Compaction throughput vs. number of compaction threads?

[Steinmaurer, Thomas]

Hello,

most likely obvious and perhaps already answered in the past, but just want to 
be sure ...

E.g. I have set:

concurrent_compactors: 4
compaction_throughput_mb_per_sec: 16

I guess this will lead to ~ 4MB/s per Thread if I have 4 compactions running in 
parallel?

So, in case of upscaling a machine and following the recommendation in 
cassandra.yaml I may set:

concurrent_compactors: 8


If this throughput remains unchanged, does this mean that we have 2 MB/s per 
Thread then, e.g. largish compactions running on a single thread taking twice 
the time then?

Using Cassandra 2.1 and 3.11 in case this matters.


Thanks a lot!
Thomas

The contents of this e-mail are intended for the named addressee only. It 
contains information that may be confidential. Unless you are the named 
addressee or an authorized designee, you may not copy or use it, or disclose it 
to anyone else. If you received it in error please notify us immediately and 
then destroy it. Dynatrace Austria GmbH (registration number FN 91482h) is a 
company registered in Linz whose registered office is at 4040 Linz, Austria, 
Freist?dterstra?e 313