My Oracle Support Banner

Q&A On Cassandra Message Record Size And Index (Doc ID 2829555.1)

Last updated on NOVEMBER 18, 2024

Applies to:

Oracle Communications Messaging Server - Version 8.1.0 and later
Information in this document applies to any platform.

Goal


Q1. Regarding "FAQ On Cassandra-based Storage (Doc ID 2725838.1)", the answer to question #3 states:

"Messages of size < 100 MB are stored as a single record. Messages of size >100 MB are chunked into blobs of 100 MB and are stored as different records in the message table of ms_msg keyspace."

Would it be better to have a record size of something like 128k?

Q2. In this scenario, the hard-coded 100meg chunk size is failing because on the Cassandra side, there is a config option which is set to a much smaller value, per the "normal" way Cassandra is operated. Is there a config option which needs to have a higher-than-normal setting to allow for that to work?

Q3. Regarding the following:

cqlsh> desc table corp_mail_msg.message


would allow the client (the access tier system) to do a single request and receive all the chunks. What is the difference?

Q4. How many partitions are the chunks spread over?
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.