Re: Upgradesstables - PerSSTableIndexWriter.java:211 - Rejecting value

2020-03-09 Thread Surbhi Gupta 
Just to add further , I could get the code reference as below:
https://github.com/xedin/sasi/blob/master/src/java/org/apache/cassandra/db/index/sasi/disk/PerSSTableIndexWriter.java

while (analyzer.hasNext())
{
ByteBuffer token = analyzer.next();
int size = token.remaining();
if (token.remaining() >= OnDiskIndexBuilder.MAX_TERM_SIZE)
{
logger.info("Rejecting value (size {}, maximum {} bytes) for column {}
(analyzed {}) at {} SSTable.",
term.remaining(),
OnDiskIndexBuilder.MAX_TERM_SIZE,
columnIndex.getColumnName(),
columnIndex.getMode().isAnalyzed,
descriptor);
continue;
}

On Mon, 9 Mar 2020 at 09:36, Surbhi Gupta  wrote:

>
> https://javadoc.io/static/org.apache.cassandra/cassandra-all/3.11.4/constant-values.html#org.apache.cassandra.index.sasi.disk.OnDiskIndexBuilder.MAX_TERM_SIZE
> The MAX_TERM_SIZE value is 1024
>
> Can we change it ?
>
>
> The messages below is INFO but because it is saying "Rejecting value" , I
> would like to understand the impact of this rejection.
>
> On Mon, 9 Mar 2020 at 08:47, Surbhi Gupta 
> wrote:
>
>> We have SASI index .
>> Any solution ?
>>
>> On Thu, 5 Mar 2020 at 15:20, Surbhi Gupta 
>> wrote:
>>
>>> Hi,
>>>
>>> We are in process of upgrading from 3.11.0 to 3.115 .
>>> While upgrading SSTables we are noticing messages like below in
>>> system.log.
>>> What are the significance of these messages?
>>>
>>> INFO  [CompactionExecutor:3] 2020-03-05 16:12:41,393
>>> PerSSTableIndexWriter.java:211 - Rejecting value (size 1.022KiB, maximum
>>> 1.000KiB) for column body (analyzed true) at
>>> /mnt/cdata/golf/enus-76e27eb0f4c111e7b07c8dd03431d478/md-196-big SSTable.
>>>
>>> INFO  [CompactionExecutor:3] 2020-03-05 16:12:41,396
>>> PerSSTableIndexWriter.java:211 - Rejecting value (size 1.178KiB, maximum
>>> 1.000KiB) for column body (analyzed true) at
>>> /mnt/cdata/golf/enus-76e27eb0f4c111e7b07c8dd03431d478/md-196-big SSTable.
>>>
>>> INFO  [CompactionExecutor:3] 2020-03-05 16:12:41,400
>>> PerSSTableIndexWriter.java:211 - Rejecting value (size 2.808KiB, maximum
>>> 1.000KiB) for column body (analyzed true) at
>>> /mnt/cdata/golf/enus-76e27eb0f4c111e7b07c8dd03431d478/md-196-big SSTable.
>>>
>>> INFO  [CompactionExecutor:3] 2020-03-05 16:12:41,401
>>> PerSSTableIndexWriter.java:211 - Rejecting value (size 1.562KiB, maximum
>>> 1.000KiB) for column body (analyzed true) at
>>> /mnt/cdata/golf/enus-76e27eb0f4c111e7b07c8dd03431d478/md-196-big SSTable.
>>>
>>> INFO  [CompactionExecutor:3] 2020-03-05 16:12:41,401
>>> PerSSTableIndexWriter.java:211 - Rejecting value (size 1.182KiB, maximum
>>> 1.000KiB) for column body (analyzed true) at
>>> /mnt/cdata/golf/enus-76e27eb0f4c111e7b07c8dd03431d478/md-196-big SSTable.
>>>
>>> INFO  [CompactionExecutor:3] 2020-03-05 16:12:41,404
>>> PerSSTableIndexWriter.java:211 - Rejecting value (size 1.848KiB, maximum
>>> 1.000KiB) for column body (analyzed true) at
>>> /mnt/cdata/golf/enus-76e27eb0f4c111e7b07c8dd03431d478/md-196-big SSTable.
>>>
>>> Thanks
>>> Surbhi
>>>
>>

Re: Upgradesstables - PerSSTableIndexWriter.java:211 - Rejecting value

2020-03-09 Thread Surbhi Gupta 
https://javadoc.io/static/org.apache.cassandra/cassandra-all/3.11.4/constant-values.html#org.apache.cassandra.index.sasi.disk.OnDiskIndexBuilder.MAX_TERM_SIZE
The MAX_TERM_SIZE value is 1024

Can we change it ?


The messages below is INFO but because it is saying "Rejecting value" , I
would like to understand the impact of this rejection.

On Mon, 9 Mar 2020 at 08:47, Surbhi Gupta  wrote:

> We have SASI index .
> Any solution ?
>
> On Thu, 5 Mar 2020 at 15:20, Surbhi Gupta 
> wrote:
>
>> Hi,
>>
>> We are in process of upgrading from 3.11.0 to 3.115 .
>> While upgrading SSTables we are noticing messages like below in
>> system.log.
>> What are the significance of these messages?
>>
>> INFO  [CompactionExecutor:3] 2020-03-05 16:12:41,393
>> PerSSTableIndexWriter.java:211 - Rejecting value (size 1.022KiB, maximum
>> 1.000KiB) for column body (analyzed true) at
>> /mnt/cdata/golf/enus-76e27eb0f4c111e7b07c8dd03431d478/md-196-big SSTable.
>>
>> INFO  [CompactionExecutor:3] 2020-03-05 16:12:41,396
>> PerSSTableIndexWriter.java:211 - Rejecting value (size 1.178KiB, maximum
>> 1.000KiB) for column body (analyzed true) at
>> /mnt/cdata/golf/enus-76e27eb0f4c111e7b07c8dd03431d478/md-196-big SSTable.
>>
>> INFO  [CompactionExecutor:3] 2020-03-05 16:12:41,400
>> PerSSTableIndexWriter.java:211 - Rejecting value (size 2.808KiB, maximum
>> 1.000KiB) for column body (analyzed true) at
>> /mnt/cdata/golf/enus-76e27eb0f4c111e7b07c8dd03431d478/md-196-big SSTable.
>>
>> INFO  [CompactionExecutor:3] 2020-03-05 16:12:41,401
>> PerSSTableIndexWriter.java:211 - Rejecting value (size 1.562KiB, maximum
>> 1.000KiB) for column body (analyzed true) at
>> /mnt/cdata/golf/enus-76e27eb0f4c111e7b07c8dd03431d478/md-196-big SSTable.
>>
>> INFO  [CompactionExecutor:3] 2020-03-05 16:12:41,401
>> PerSSTableIndexWriter.java:211 - Rejecting value (size 1.182KiB, maximum
>> 1.000KiB) for column body (analyzed true) at
>> /mnt/cdata/golf/enus-76e27eb0f4c111e7b07c8dd03431d478/md-196-big SSTable.
>>
>> INFO  [CompactionExecutor:3] 2020-03-05 16:12:41,404
>> PerSSTableIndexWriter.java:211 - Rejecting value (size 1.848KiB, maximum
>> 1.000KiB) for column body (analyzed true) at
>> /mnt/cdata/golf/enus-76e27eb0f4c111e7b07c8dd03431d478/md-196-big SSTable.
>>
>> Thanks
>> Surbhi
>>
>

slurm for cluster job scheduling and coordination

2020-03-09 Thread Carl Mueller 
Between repairs, rolling restarts, scheduled maintenance bounces, backups,
upgrades, etc there are lots of cluster-wide tasks that would be nice to be
scheduled and viewed.

Slurm appears to have some features that support this but might be
heavyweight considering its primary application is supercomputer job
scheduling.

I'd like something kinda independent of cloud vendor, container/VM/metal
strategies, or specific "cloud os".

Anyone tried slurm or have an alternative? I really don't want to write
yet-another-scheduler.

Re: Upgradesstables - PerSSTableIndexWriter.java:211 - Rejecting value

2020-03-09 Thread Surbhi Gupta 
We have SASI index .
Any solution ?

On Thu, 5 Mar 2020 at 15:20, Surbhi Gupta  wrote:

> Hi,
>
> We are in process of upgrading from 3.11.0 to 3.115 .
> While upgrading SSTables we are noticing messages like below in system.log.
> What are the significance of these messages?
>
> INFO  [CompactionExecutor:3] 2020-03-05 16:12:41,393
> PerSSTableIndexWriter.java:211 - Rejecting value (size 1.022KiB, maximum
> 1.000KiB) for column body (analyzed true) at
> /mnt/cdata/golf/enus-76e27eb0f4c111e7b07c8dd03431d478/md-196-big SSTable.
>
> INFO  [CompactionExecutor:3] 2020-03-05 16:12:41,396
> PerSSTableIndexWriter.java:211 - Rejecting value (size 1.178KiB, maximum
> 1.000KiB) for column body (analyzed true) at
> /mnt/cdata/golf/enus-76e27eb0f4c111e7b07c8dd03431d478/md-196-big SSTable.
>
> INFO  [CompactionExecutor:3] 2020-03-05 16:12:41,400
> PerSSTableIndexWriter.java:211 - Rejecting value (size 2.808KiB, maximum
> 1.000KiB) for column body (analyzed true) at
> /mnt/cdata/golf/enus-76e27eb0f4c111e7b07c8dd03431d478/md-196-big SSTable.
>
> INFO  [CompactionExecutor:3] 2020-03-05 16:12:41,401
> PerSSTableIndexWriter.java:211 - Rejecting value (size 1.562KiB, maximum
> 1.000KiB) for column body (analyzed true) at
> /mnt/cdata/golf/enus-76e27eb0f4c111e7b07c8dd03431d478/md-196-big SSTable.
>
> INFO  [CompactionExecutor:3] 2020-03-05 16:12:41,401
> PerSSTableIndexWriter.java:211 - Rejecting value (size 1.182KiB, maximum
> 1.000KiB) for column body (analyzed true) at
> /mnt/cdata/golf/enus-76e27eb0f4c111e7b07c8dd03431d478/md-196-big SSTable.
>
> INFO  [CompactionExecutor:3] 2020-03-05 16:12:41,404
> PerSSTableIndexWriter.java:211 - Rejecting value (size 1.848KiB, maximum
> 1.000KiB) for column body (analyzed true) at
> /mnt/cdata/golf/enus-76e27eb0f4c111e7b07c8dd03431d478/md-196-big SSTable.
>
> Thanks
> Surbhi
>

Re: Data not persisted in Cassandra docker

2020-03-09 Thread Cedrick Lunven 
Hi, here is a sample docker-compose.yaml for what you need.

version: '2'
services:
  cassandra:
image: cassandra:3.11.5
ports:
  - 7000:7000
  - 7001:7001
  - 7199:7199
  - 9042:9042
  - 9160:9160
ulimits:
  memlock: -1
volumes:
   - ~/cassandra/:/var/lib/cassandra/data



On Mon, Mar 9, 2020 at 10:30 AM Hannu Kröger  wrote:

> You need to mount volumes from the host system or docker volumes to
> container to have data persisted.
>
> See section "Where to Store Data” in https://hub.docker.com/_/cassandra
> 
>
> Hannu
>
> On 9. Mar 2020, at 11.25, Valentina Ivanova 
> wrote:
>
> Hello!
>
> I am using Cassandra 3.11.5 from docker. I created a keyspace and a table
> in it and inserted some data into the table. Before stopping the container
> I executed nodetool flush to persist the data. However, upon starting the
> container after the weekend, the keyspace, table and data were not
> existent. What shall I do in order to persist the data?
>
> Many thanks & have a great week!
>
> Valentina
>
>
>

-- 


*Cédrick Lunven | *EMEA Developer Advocate


*🎓**Free Trainings : *DataStax Academy * ❓**Ask
us your questions** :* DataStax Community
* 🔬**Test our new
products** : *DataStax
Labs

Re: Data not persisted in Cassandra docker

2020-03-09 Thread Hannu Kröger 
You need to mount volumes from the host system or docker volumes to container 
to have data persisted.

See section "Where to Store Data” in https://hub.docker.com/_/cassandra 


Hannu

> On 9. Mar 2020, at 11.25, Valentina Ivanova  wrote:
> 
> Hello!
> 
> I am using Cassandra 3.11.5 from docker. I created a keyspace and a table in 
> it and inserted some data into the table. Before stopping the container I 
> executed nodetool flush to persist the data. However, upon starting the 
> container after the weekend, the keyspace, table and data were not existent. 
> What shall I do in order to persist the data?
> 
> Many thanks & have a great week!
> 
> Valentina

Data not persisted in Cassandra docker

2020-03-09 Thread Valentina Ivanova 
Hello!

I am using Cassandra 3.11.5 from docker. I created a keyspace and a table in it 
and inserted some data into the table. Before stopping the container I executed 
nodetool flush to persist the data. However, upon starting the container after 
the weekend, the keyspace, table and data were not existent. What shall I do in 
order to persist the data?

Many thanks & have a great week!

Valentina