: Dor Laor
Sent: Wednesday, January 09, 2019 11:23 PM
To: user@cassandra.apache.org
Subject: Re: [EXTERNAL] Re: Good way of configuring Apache spark with Apache
Cassandra
On Wed, Jan 9, 2019 at 7:28 AM Durity, Sean R
mailto:sean_r_dur...@homedepot.com>> wrote:
I think you could consider op
.
Sean Durity
From: Goutham reddy
Sent: Wednesday, January 09, 2019 11:29 AM
To: user@cassandra.apache.org
Subject: Re: [EXTERNAL] Re: Good way of configuring Apache spark with Apache
Cassandra
Thanks Sean. But what if I want to have both Spark and elasticsearch with
Cassandra as separare data
altime workload for
isolation and low latency guarantees.
We addressed this problem elsewhere, beyond this scope.
>
>
>
> Sean Durity
>
>
>
> *From:* Dor Laor
> *Sent:* Friday, January 04, 2019 4:21 PM
> *To:* user@cassandra.apache.org
> *Subject:* [EX
Friday, January 04, 2019 4:21 PM
> *To:* user@cassandra.apache.org
> *Subject:* [EXTERNAL] Re: Good way of configuring Apache spark with
> Apache Cassandra
>
>
>
> I strongly recommend option B, separate clusters. Reasons:
>
> - Networking of node-node is negligible compared
From: Dor Laor
Sent: Friday, January 04, 2019 4:21 PM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Re: Good way of configuring Apache spark with Apache
Cassandra
I strongly recommend option B, separate clusters. Reasons:
- Networking of node-node is negligible compared to networking within
Thanks Jonathan, I believe we have to reconsider the way analytics have to
be performed.
On Fri, Jan 4, 2019 at 1:46 PM Jonathan Haddad wrote:
> If you absolutely have to use Cassandra as the source of your data, I
> agree with Dor.
>
> That being said, if you're going to be doing a lot of
If you absolutely have to use Cassandra as the source of your data, I agree
with Dor.
That being said, if you're going to be doing a lot of analytics, I
recommend using something other than Cassandra with Spark. The performance
isn't particularly wonderful and you'll likely get anywhere from
Thank you very much Dor for the detailed information, yes that should be
the primary reason why we have to isolate from Cassandra.
Thanks and Regards,
Goutham Reddy
On Fri, Jan 4, 2019 at 1:29 PM Dor Laor wrote:
> I strongly recommend option B, separate clusters. Reasons:
> - Networking of
I strongly recommend option B, separate clusters. Reasons:
- Networking of node-node is negligible compared to networking within the
node
- Different scaling considerations
Your workload may require 10 Spark nodes and 20 database nodes, so why
bundle them?
This ratio may also change over
Hi,
We have requirement of heavy data lifting and analytics requirement and
decided to go with Apache Spark. In the process we have come up with two
patterns
a. Apache Spark and Apache Cassandra co-located and shared on same nodes.
b. Apache Spark on one independent cluster and Apache Cassandra as
10 matches
Mail list logo
