Triggers and their use in data indexing

[Bèrto ëd Sèra <be...@gmail.com>]

Hi all,

we are planning a set of 3 data-centres (each located in a different
continent). There is a possibility that the connection among them will
occasionally fail for an unforeseeable length of time. The quorum would be
limited to the local data-centre, as each user access his local
data-centre, with the set of 3 "eventually consistent" as a picture of the
entire business.

The delicate bit is that we also have a search-engine. To insulate it from
network issues among data-centres we would like to have one for each DC.
Data would be indexed per-DC, as soon as it gets locally available.

Now the question: is there any way to use triggers so that they will
locally index data from remote DCs when it comes in?

We are in a very early stage of planning, and I am just trying to make sure
that what we plan makes basic sense, as I never used C* triggers and I am
not sure I get all the implications. The search engine is likely to be
ElasticSearch, though this is not cast in stone ATM.

Cheers
Bèrto

-- 
==============================
If Pac-Man had affected us as kids, we'd all be running around in a
darkened room munching pills and listening to repetitive music.

Re: Triggers and their use in data indexing

[Jonathan Haddad <jo...@jonhaddad.com>]

This is one of the trickier areas of doing multi dc.  The current
recommendation is to use a separate message queue.

If you'd like to see remote triggers, you could fire a JIRA.  Get back
to the list w/ the ticket #, I'm sure there are others who have
similar needs.

On Thu, Jul 3, 2014 at 10:04 AM, Jonathan Haddad <jo...@jonhaddad.com> wrote:
> Triggers only execute on the local coordinator.  I would also not
> recommend using them.
>
> On Thu, Jul 3, 2014 at 9:58 AM, Robert Coli <rc...@eventbrite.com> wrote:
>> On Thu, Jul 3, 2014 at 4:41 AM, Bèrto ëd Sèra <be...@gmail.com>
>> wrote:
>>>
>>> Now the question: is there any way to use triggers so that they will
>>> locally index data from remote DCs when it comes in?
>>
>>
>> As I understand it, you probably should not use triggers in production in
>> their current form.
>>
>> =Rob
>>
>
>
>
> --
> Jon Haddad
> http://www.rustyrazorblade.com
> skype: rustyrazorblade



-- 
Jon Haddad
http://www.rustyrazorblade.com
skype: rustyrazorblade

Re: Triggers and their use in data indexing

[Jonathan Haddad <jo...@jonhaddad.com>]

Triggers only execute on the local coordinator.  I would also not
recommend using them.

On Thu, Jul 3, 2014 at 9:58 AM, Robert Coli <rc...@eventbrite.com> wrote:
> On Thu, Jul 3, 2014 at 4:41 AM, Bèrto ëd Sèra <be...@gmail.com>
> wrote:
>>
>> Now the question: is there any way to use triggers so that they will
>> locally index data from remote DCs when it comes in?
>
>
> As I understand it, you probably should not use triggers in production in
> their current form.
>
> =Rob
>



-- 
Jon Haddad
http://www.rustyrazorblade.com
skype: rustyrazorblade

Re: Triggers and their use in data indexing

[Robert Coli <rc...@eventbrite.com>]

On Thu, Jul 3, 2014 at 4:41 AM, Bèrto ëd Sèra <be...@gmail.com>
wrote:

> Now the question: is there any way to use triggers so that they will
> locally index data from remote DCs when it comes in?
>

As I understand it, you probably should not use triggers in production in
their current form.

=Rob