You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by tomk <rr...@gmail.com> on 2016/05/25 22:45:35 UTC
Two nodes in cluster
Hello,
At now I have only one node, but I am going to add more machines (in one
local network).
What should I know to do it ?
I have PARTITIONED type of cache.
Hot loading (my use case is caching postgresql) is done on one machine.
How to force ignite to distribute these rows to all machines - not only that
where client is executed (client initialize hot loading from postgresql).
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Two-nodes-in-cluster-tp5204.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Two nodes in cluster
Posted by Denis Magda <dm...@gridgain.com>.
How this topic is related to SQL queries? :)
I see that you’ve already started a bunch of SQL related topics on the user list. In short SQL queries can be executed via JDBC client or using Java API.
Refer to this page for more details - https://apacheignite.readme.io/docs/sql-queries <https://apacheignite.readme.io/docs/sql-queries>
In addition it makes sense to investigate CacheQueryExample that is delivered with Ignite releases
https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/datagrid/CacheQueryExample.java <https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/datagrid/CacheQueryExample.java>
—
Denis
> On May 26, 2016, at 7:18 PM, Tomek W <rr...@gmail.com> wrote:
>
> Ok,
> Where should I follow my SQL queries (via JDBC interface) ?
> I have two nodes with data - I would like to get full answer to SQL query.
>
> 2016-05-26 10:08 GMT+02:00 Denis Magda <dmagda@gridgain.com <ma...@gridgain.com>>:
> Ignite will automatically redistribute (rebalance) data across all available nodes. So everything is scaling horizontally automatically.
> You just need to start a new node and portion of dataset will be rebalanced on it.
>
> —
> Denis
>
>> On May 26, 2016, at 10:30 AM, Tomek W <rrrtomtomrrr@gmail.com <ma...@gmail.com>> wrote:
>>
>> Yes,
>> but I consider how to force ignite to distribute rows on other machines (not only this machine that initialized hot loading).
>>
>> 2016-05-26 8:46 GMT+02:00 Vladislav Pyatkov <vldpyatkov@gmail.com <ma...@gmail.com>>:
>> Hello,
>>
>> If I understand correctly, you want to load data from a database in PARTITIONED type cache. This case is well described here
>> https://apacheignite.readme.io/docs/data-loading <https://apacheignite.readme.io/docs/data-loading>
>>
>> On Thu, May 26, 2016 at 1:45 AM, tomk <rrrtomtomrrr@gmail.com <ma...@gmail.com>> wrote:
>> Hello,
>> At now I have only one node, but I am going to add more machines (in one
>> local network).
>> What should I know to do it ?
>> I have PARTITIONED type of cache.
>> Hot loading (my use case is caching postgresql) is done on one machine.
>> How to force ignite to distribute these rows to all machines - not only that
>> where client is executed (client initialize hot loading from postgresql).
>>
>>
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Two-nodes-in-cluster-tp5204.html <http://apache-ignite-users.70518.x6.nabble.com/Two-nodes-in-cluster-tp5204.html>
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com <http://nabble.com/>.
>>
>>
>>
>> --
>> Vladislav Pyatkov
>>
>
>
Re: Two nodes in cluster
Posted by Tomek W <rr...@gmail.com>.
Ok,
Where should I follow my SQL queries (via JDBC interface) ?
I have two nodes with data - I would like to get full answer to SQL query.
2016-05-26 10:08 GMT+02:00 Denis Magda <dm...@gridgain.com>:
> Ignite will automatically redistribute (rebalance) data across all
> available nodes. So everything is scaling horizontally automatically.
> You just need to start a new node and portion of dataset will be
> rebalanced on it.
>
> —
> Denis
>
> On May 26, 2016, at 10:30 AM, Tomek W <rr...@gmail.com> wrote:
>
> Yes,
> but I consider how to force ignite to *distribute* rows on other machines
> (*not only this machine that initialized hot loading*).
>
> 2016-05-26 8:46 GMT+02:00 Vladislav Pyatkov <vl...@gmail.com>:
>
>> Hello,
>>
>> If I understand correctly, you want to load data from a database in
>> PARTITIONED type cache. This case is well described here
>> https://apacheignite.readme.io/docs/data-loading
>>
>> On Thu, May 26, 2016 at 1:45 AM, tomk <rr...@gmail.com> wrote:
>>
>>> Hello,
>>> At now I have only one node, but I am going to add more machines (in one
>>> local network).
>>> What should I know to do it ?
>>> I have PARTITIONED type of cache.
>>> Hot loading (my use case is caching postgresql) is done on one machine.
>>> How to force ignite to distribute these rows to all machines - not only
>>> that
>>> where client is executed (client initialize hot loading from postgresql).
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://apache-ignite-users.70518.x6.nabble.com/Two-nodes-in-cluster-tp5204.html
>>> Sent from the Apache Ignite Users mailing list archive at Nabble.com
>>> <http://nabble.com>.
>>>
>>
>>
>>
>> --
>> Vladislav Pyatkov
>>
>
>
>
Re: Two nodes in cluster
Posted by Denis Magda <dm...@gridgain.com>.
Ignite will automatically redistribute (rebalance) data across all available nodes. So everything is scaling horizontally automatically.
You just need to start a new node and portion of dataset will be rebalanced on it.
—
Denis
> On May 26, 2016, at 10:30 AM, Tomek W <rr...@gmail.com> wrote:
>
> Yes,
> but I consider how to force ignite to distribute rows on other machines (not only this machine that initialized hot loading).
>
> 2016-05-26 8:46 GMT+02:00 Vladislav Pyatkov <vldpyatkov@gmail.com <ma...@gmail.com>>:
> Hello,
>
> If I understand correctly, you want to load data from a database in PARTITIONED type cache. This case is well described here
> https://apacheignite.readme.io/docs/data-loading <https://apacheignite.readme.io/docs/data-loading>
>
> On Thu, May 26, 2016 at 1:45 AM, tomk <rrrtomtomrrr@gmail.com <ma...@gmail.com>> wrote:
> Hello,
> At now I have only one node, but I am going to add more machines (in one
> local network).
> What should I know to do it ?
> I have PARTITIONED type of cache.
> Hot loading (my use case is caching postgresql) is done on one machine.
> How to force ignite to distribute these rows to all machines - not only that
> where client is executed (client initialize hot loading from postgresql).
>
>
>
>
>
> --
> View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Two-nodes-in-cluster-tp5204.html <http://apache-ignite-users.70518.x6.nabble.com/Two-nodes-in-cluster-tp5204.html>
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
>
>
> --
> Vladislav Pyatkov
>
Re: Two nodes in cluster
Posted by Vladislav Pyatkov <vl...@gmail.com>.
Data themselves are distributed across nodes (in the PARTITIONED cache) is
responsible for this affinity function.
You can follow any responses to write his affinity functions are
implemented org.apache.ignite.cache.affinity.AffinityFunction and install
it via the configuration cache
org.apache.ignite.configuration.CacheConfiguration # setAffinity
On Thu, May 26, 2016 at 10:30 AM, Tomek W <rr...@gmail.com> wrote:
> Yes,
> but I consider how to force ignite to *distribute* rows on other machines
> (*not only this machine that initialized hot loading*).
>
> 2016-05-26 8:46 GMT+02:00 Vladislav Pyatkov <vl...@gmail.com>:
>
>> Hello,
>>
>> If I understand correctly, you want to load data from a database in
>> PARTITIONED type cache. This case is well described here
>> https://apacheignite.readme.io/docs/data-loading
>>
>> On Thu, May 26, 2016 at 1:45 AM, tomk <rr...@gmail.com> wrote:
>>
>>> Hello,
>>> At now I have only one node, but I am going to add more machines (in one
>>> local network).
>>> What should I know to do it ?
>>> I have PARTITIONED type of cache.
>>> Hot loading (my use case is caching postgresql) is done on one machine.
>>> How to force ignite to distribute these rows to all machines - not only
>>> that
>>> where client is executed (client initialize hot loading from postgresql).
>>>
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://apache-ignite-users.70518.x6.nabble.com/Two-nodes-in-cluster-tp5204.html
>>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>>
>>
>>
>>
>> --
>> Vladislav Pyatkov
>>
>
>
--
Vladislav Pyatkov
Re: Two nodes in cluster
Posted by Tomek W <rr...@gmail.com>.
Yes,
but I consider how to force ignite to *distribute* rows on other machines (*not
only this machine that initialized hot loading*).
2016-05-26 8:46 GMT+02:00 Vladislav Pyatkov <vl...@gmail.com>:
> Hello,
>
> If I understand correctly, you want to load data from a database in
> PARTITIONED type cache. This case is well described here
> https://apacheignite.readme.io/docs/data-loading
>
> On Thu, May 26, 2016 at 1:45 AM, tomk <rr...@gmail.com> wrote:
>
>> Hello,
>> At now I have only one node, but I am going to add more machines (in one
>> local network).
>> What should I know to do it ?
>> I have PARTITIONED type of cache.
>> Hot loading (my use case is caching postgresql) is done on one machine.
>> How to force ignite to distribute these rows to all machines - not only
>> that
>> where client is executed (client initialize hot loading from postgresql).
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://apache-ignite-users.70518.x6.nabble.com/Two-nodes-in-cluster-tp5204.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>
>
> --
> Vladislav Pyatkov
>
Re: Two nodes in cluster
Posted by Vladislav Pyatkov <vl...@gmail.com>.
Hello,
If I understand correctly, you want to load data from a database in
PARTITIONED type cache. This case is well described here
https://apacheignite.readme.io/docs/data-loading
On Thu, May 26, 2016 at 1:45 AM, tomk <rr...@gmail.com> wrote:
> Hello,
> At now I have only one node, but I am going to add more machines (in one
> local network).
> What should I know to do it ?
> I have PARTITIONED type of cache.
> Hot loading (my use case is caching postgresql) is done on one machine.
> How to force ignite to distribute these rows to all machines - not only
> that
> where client is executed (client initialize hot loading from postgresql).
>
>
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Two-nodes-in-cluster-tp5204.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
--
Vladislav Pyatkov