Tables showing up as our_table-147a2090ed4211e480153bc81e542ebd/ in data dir

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Tables showing up as our_table-147a2090ed4211e480153bc81e542ebd/ in data dir

Donald Smith

Using 2.1.4, tables in our data/ directory are showing up as


            our_table-147a2090ed4211e480153bc81e542ebd/ 


instead of as


             our_table/


Why would that happen? We're also seeing lagging compactions and high cpu usage.


 Thanks, Don

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Tables showing up as our_table-147a2090ed4211e480153bc81e542ebd/ in data dir

Peer, Oded

See https://github.com/apache/cassandra/blob/trunk/NEWS.txt#L173

 

SSTable data directory name is slightly changed. Each directory will have hex string appended after CF name, e.g. ks/cf-5be396077b811e3a3ab9dc4b9ac088d/

This hex string part represents unique ColumnFamily ID.

Note that existing directories are used as is, so only newly created directories after upgrade have new directory name format.

 

 

From: Donald Smith [mailto:[hidden email]]
Sent: Wednesday, April 29, 2015 8:04 AM
To: [hidden email]
Subject: Tables showing up as our_table-147a2090ed4211e480153bc81e542ebd/ in data dir

 

Using 2.1.4, tables in our data/ directory are showing up as

 

            our_table-147a2090ed4211e480153bc81e542ebd/ 

 

instead of as

 

             our_table/

 

Why would that happen? We're also seeing lagging compactions and high cpu usage.

 

 Thanks, Don

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tables showing up as our_table-147a2090ed4211e480153bc81e542ebd/ in data dir

Yuki Morishita
In reply to this post by Donald Smith
Directory structure is changed in 2.1 to prevent various problems
caused by DROP/re-CREATE the same table
(https://issues.apache.org/jira/browse/CASSANDRA-5202).
From NEWS.txt:

2.1
===
New features
------------
   ...
   - SSTable data directory name is slightly changed. Each directory will
      have hex string appended after CF name, e.g.
          ks/cf-5be396077b811e3a3ab9dc4b9ac088d/
      This hex string part represents unique ColumnFamily ID.
      Note that existing directories are used as is, so only newly created
      directories after upgrade have new directory name format.

On Wed, Apr 29, 2015 at 2:04 PM, Donald Smith
<[hidden email]> wrote:

> Using 2.1.4, tables in our data/ directory are showing up as
>
>
>             our_table-147a2090ed4211e480153bc81e542ebd/
>
>
> instead of as
>
>
>              our_table/
>
>
> Why would that happen? We're also seeing lagging compactions and high cpu
> usage.
>
>
>  Thanks, Don



--
Yuki Morishita
 t:yukim (http://twitter.com/yukim)
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Tables showing up as our_table-147a2090ed4211e480153bc81e542ebd/ in data dir

Philo Yang
In reply to this post by Donald Smith
see https://github.com/apache/cassandra/blob/cassandra-2.1/NEWS.txt#L77

SSTable data directory name will have hex string appended after CF name

2015-04-29 13:04 GMT+08:00 Donald Smith <[hidden email]>:

Using 2.1.4, tables in our data/ directory are showing up as


            our_table-147a2090ed4211e480153bc81e542ebd/ 


instead of as


             our_table/


Why would that happen? We're also seeing lagging compactions and high cpu usage.


 Thanks, Don




--
Thanks,
Phil Yang

Loading...