Clay,
Probably, such frameworks as Quarkus, Spring Boot, Micronaut would work as
a better foundation for your microservices. As you know, those already go
with embedded REST servers and you can always use Ignite clients to
reach out to the cluster.
Usually, Ignite servers are deployed in the embe
Can someone please help me with this issue.
On Sat, Jun 6, 2020 at 6:45 PM Akash Shinde wrote:
> Hi,
> Issue: Countdown latched gets reinitialize to original value(4) when one
> or more (but not all) node goes down. (Partition loss happened)
>
> We are using ignite's distributed countdownlatch t
So once I insert an instance of a class in a Map I can't change the type of
any existing member variable in the class, even if I clear the map?
Seems like there should be some programatic way to clear any left-over
class metadata/schema if simply clearing the cache won't do it. Right?
On Sat, Jun
Hi Denis -- My main reason was for embedding jetty as an ignite service was
to have ignite manage jetty instance, the same it does for any other kind
of service.
On Thu, Jun 4, 2020 at 3:30 PM Denis Magda wrote:
> Clay,
>
> Do you have any specific requirements in mind for the ignite service +
>
You might have hit the following specificity ("Cluster Doesn’t Start After
Field Type Changes") that happens if you change a type of a field:
https://www.gridgain.com/docs/latest/perf-troubleshooting-guide/troubleshooting#cluster-doesnt-start-after-field-type-changes
-
Denis
On Fri, Jun 5, 2020
*Issue:* Countdown latched gets reinitialize to original value(4) when one
or more (but not all) node goes down. *(Partition loss happened)*
We are using ignite's distributed countdownlatch to make sure that cache
loading is completed on all server nodes. We do this to make sure that our
kafka con
Hi,
Issue: Countdown latched gets reinitialize to original value(4) when one or
more (but not all) node goes down. (Partition loss happened)
We are using ignite's distributed countdownlatch to make sure that cache
loading is completed on all server nodes. We do this to make sure that our
kafka con
In our project we are currently using ignite 2.7.6 with native persistence
disabled and java 11. At the moment we are not using the on-heap feature,
i.e. all our data lives in off-heap. However in order to gain performance we
are thinking about activating on-heap. While there are already quite many
