Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DC-Specific indexing #67

Open
mark1ewis opened this issue Oct 20, 2015 · 3 comments
Open

DC-Specific indexing #67

mark1ewis opened this issue Oct 20, 2015 · 3 comments

Comments

@mark1ewis
Copy link

It would help support mixed clusters if Stargate could index only in a specific DC, so for example the reporting DC could pay the secondary-index overhead for using Stargate without impacting the OLTP nodes.

Ideally, it would be nice to not need to have Stargate installed on the production OLTP nodes at all, but not sure if that's feasible.

@trulite
Copy link
Member

trulite commented Oct 22, 2015

I wrote a comment earlier about doing it on a per-node configuration basis, but that would complicate querying. So I will think a bit more about this.

@mark1ewis
Copy link
Author

Ideally it could be enabled on a per-DC basis. That's the way that DSE
Search works, and seems like it would help resolve the querying issue. It
would be fine if stargate queries made to nodes outside of the configured
DC nodes failed I think.
On Oct 22, 2015 10:54 AM, "Satyaprakash Buddhavarapu" <
[email protected]> wrote:

I wrote a comment earlier about doing it on a per-node configuration
basis, but that would complicate querying. So I will think a bit more about
this.


Reply to this email directly or view it on GitHub
#67 (comment)
.

@trulite
Copy link
Member

trulite commented Oct 28, 2015

Okay the DC aware indexing seems possible, but would require a lot of testing. If there is readiness to help in testing, this can be implemented.
If you are in the mood to get your hands dirty, I can point out the relevant areas to make changes and test. Otherwise we can make the changes except the change -> test -> change cycle will be longer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants