+1
On Fri, May 26, 2023 at 7:31 AM Aleksey Yeshchenko
wrote:
> +1
>
> On 26 May 2023, at 07:19, Berenguer Blasi
> wrote:
>
> +1
> On 26/5/23 6:07, guo Maxwell wrote:
>
> +1
>
> Dinesh Joshi 于2023年5月26日 周五上午11:08写道：
>
>> +1
>>
>>
>> On May 25, 2023, at 8:45 AM, Jonathan Ellis wrote:
>>
>>
>>
VtjMegQ9c2l2zDzHAxiU&e=>
[image: Twitter Logo] <https://twitter.com/DataStax> [image: RSS Feed]
<https://www.datastax.com/blog/rss.xml> [image: Github Logo]
<https://github.com/datastax>
Find DataStax Online:
[image: DataStax Logo Square] <https://www.datastax.com>
*Stefania Alborghetti*
Cloud engineering
+1 650 389 6000 <16503896000> | datastax.com <https://www.datastax.com>
d.
>
> The logs show no errors.
>
> Any suggestions?
>
> Thanks,
> Michael
>
>
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>
--
<http:
i think that would be a good idea
>
--
<http://www.datastax.com/>
STEFANIA ALBORGHETTI
Software engineer | +852 6114 9265 | stefania.alborghe...@datastax.com
[image: http://www.datastax.com/cloud-applications]
<http://www.datastax.com/cloud-applications>
gt; > so there's a theoretical maximum op size we'd want to use to stay under
> > > that throughput limit. Alternatively, we could also tune compaction
> > > throughput to maintain that limit too.
> > >
> > > Has any work been done to optimize sequential I
hat case, due to the changes
> outlined CASSANDRA-9548/CASSANDRA-8709/CASSANDRA-5863, there should
> probably be a warning in 3.6 that buffer_pool_use_heap_if_exhausted should
> be set to false if you still have some tables on SnappyCompression.
>
> Nimi
>
> On We
; CASSANDRA-11993 goes away (I think? I'm having a number of issues lately
> and I may have traded one exception for another).
>
> Is this the correct behavior of buffer_pool_use_heap_if_exhausted?
>
> Nimi
>
--
[image: datastax_logo.png] <http://www.datastax.com/>
Stefania Alborghetti
Apache Cassandra Software Engineer
|+852 6114 9265| stefania.alborghe...@datastax.com
[image: cassandrasummit.org/Email_Signature]
<http://cassandrasummit.org/Email_Signature>
s could use a standard disk
> access mode reader with configurable block size while normal read
> operations stuck to the mmap'd segments. Being unfamiliar with the code,
> are compaction/sequential sstable reads done through any single interface
> or does it use the same as normal read
owse/CASSANDRA-11765
>
> As mentioned in our report (https://goo.gl/hNyrnW), CASSANDRA-11663
> may have been addressed by the fix for a resolved ticket, and
> CASSANDRA-11765 is currently marked Patch Available. Please see the
> report for more details.
>
--
[image:
he/cassandra/stress/generate/values/Strings.java.
Changing this line:
chars[i++] = (char) (((v & 127) + 32) & 127);
with this:
chars[i++] = (char) (((v & 127) % 95) + 32);
should work but I could not avoid the expensive modulo operation. You can
rebuild cassandra-stress with ant stre
; > http://people.apache.org/~jake
> > >
> > > The vote will be open for 48 hours (longer if needed).
> > >
> > > [1]: http://goo.gl/dmpzjR (CHANGES.txt)
> > > [2]: http://goo.gl/ACOC01 (NEWS.txt)
> > >
> >
>
--
[image: datastax_logo.png] <http://www.datastax.com/>
Stefania Alborghetti
Apache Cassandra Software Engineer
|+852 6114 9265| stefania.alborghe...@datastax.com
; > http://people.apache.org/~jake
> > >
> > > The vote will be open for 48 hours (longer if needed).
> > >
> > > [1]: http://goo.gl/cfjxJU (CHANGES.txt)
> > > [2]: http://goo.gl/nOz2X6 (NEWS.txt)
> > >
> >
>
--
[image: datastax_logo.png] <http://www.datastax.com/>
Stefania Alborghetti
Apache Cassandra Software Engineer
|+852 6114 9265| stefania.alborghe...@datastax.com
12 matches
Mail list logo
