I can tell you as a user that if any library I was using in my application
called System.exit without my consent would result in a lot of frustration.
If ignite enters an unrecoverable state then I think that is something that
should be observable locally, similar to node segmentation and then the
Ray,
I think to avoid excessive GC and OOM you could try switching to a lazy
result set:
https://apacheignite-sql.readme.io/docs/performance-and-debugging#result-set-lazy-load
- Nick
On Wed, Nov 29, 2017, 7:19 AM Anton Vinogradov
wrote:
> Ray,
>
> Seems you're looking
> for org.apache.ignite.c
How is a user expected to produce a collection of ClusterNode prior to all
of the expected nodes joining? Users don't create instances of this, so as
far as I can tell it would have to be retrieved from IgniteCluster.
However, would doing that and calling the proposed method be really any
different
ld and deploy uber-jars that has no external
> dependencies?
>
> -Val
>
> On Sun, Aug 20, 2017 at 1:02 PM, Nick Pordash
> wrote:
>
> > If the dependency is not exposed by the public API then another
> alternative
> > is to simply shade the artifact and then
The notion of saving changes to a configuration file does not make sense
for lots of use cases, Kubernetes is one example. Anything in the
container's filesystem is considered transient since it will get destroyed
when a pod is restarted.
I would think that runtime changes should be managed in the
If the dependency is not exposed by the public API then another alternative
is to simply shade the artifact and then this becomes a non-issue for
users.
Considering Ignite is a platform that executes user code via compute and
service grid I personally think it would be good to minimize the number
Hi Dmitriy,
The ticket was a regression from 1.9 to 2.0. I don't think anyone would be
expecting the behavior in 2.0 as it doesn't align with the javadoc and has
only been broken since the 2.0 release.
-Nick
On Wed, Jul 19, 2017, 6:55 AM Dmitry Pavlov wrote:
> Hi Evgeniy,
>
> Thank you. Ignite
Nick Pordash created IGNITE-5123:
Summary: Ignite.cache(String) returns null in
PluginProvider.onIgniteStart()
Key: IGNITE-5123
URL: https://issues.apache.org/jira/browse/IGNITE-5123
Project: Ignite
