Hello!

See below inline:

пт, 15 мая 2020 г. в 23:59, nithin91 <
[email protected]>:

> Hi
>
> Although this seems to be working.
> I have following queries with this approach.Can you please
> provide your inputs/suggestions.
>
>
>
>                         We are going to expose this SpringBoot
>                         App as a RestFul API where we are trying to
>                         refresh the Ignite Cache by sending  request to
> this
>                         Application whenever the data in Oracle changes.
>                         .
>                         As we are trying to expose this APP as a API,
>                         which means that this  Ignite Client Node
>                         instance launched from Spring boot Application
> will
>                         be active for ever.Now my queries are
>
>                         1. Is it ok to have a client node which
>                         is continously in connected state forever.
>                         If Ok,then how many such client node can exist.
>
Yes, it's OK, you can have dozens of clients connected at all times.

                        2. Can this Application, be hosted on the
>                         one of the server node with different port.
>
Yes. No additional configuration is necessary.


>                         3. Also will client node connect automatically
>                         to the cluster if the client node has  lost
>                         communication with server because if the client
>                         node is down and if there is an API request
>                         , then the application will throw an error.
>
Client will try to reconnect automatically. It will throw ClientNode
IgniteClientDisconnectedException in the meantime.


>                         4. Is this way of refreshing the cache is
> efficient.
>                         If no, can you please suggest a better way.
>
What do you mean by refreshing cache?


>                         5. Also take provide an example on the possibility
>                         of  having the REST API calling a
>                         compute job which would
>                         execute in a separate server
>                         https://apacheignite.readme.io/docs/compute-grid
>         Also i have few more queries related to Ignite
>         Behaviour.It would be really helpful if you can
>         provide some inputs.
>
>         1. Currently we are using
>                 ignite.cache("CacheName").loadCache(null) method
>                 to load  the cache initially and also increamentally as
>                 this method loads data very fast almost 0.1 million
>                 in 1 minute. For increamental load also  we are using this
> method
>                 by passing an additional argument i.e. Custom
>                 Sql  to load/update only the records that have
> created/changed.
>                 but what is happening is if the key doesn't
>                 exist it is inserting the data  but if the key is present
>                 it is not updating its value.
>                 Why is the value not updated if the key is present.
>
This is by design.


>
>         2. To overcome this, i have to build my own custom
>         cache store as mentioned in the following link
>         https://apacheignite.readme.io/v1.9/docs/data-loading.
>         But the problem with this approach is  i need to use JDBC
>         result set to load the data which is very slow as
>         we have to insert row by row.
>         Is there a better way to update the keys.
>
Consider using DataStreamer.


>
>
>         3. How to load data faster with custom cache store
>         as loading the data which is very slow as
>         we have to insert row by row.
>
See above.

Regards,
-- 
Ilya.


>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Reply via email to