Hello Vladimir,
> What we can do is to optionally disable on-heap caching for specific set at
> the cost of lower performance if user wants so.
I want to make sure that we are speaking about the same thing. By
"on-heap caching" I mean custom datastructure and not standard on-heap
cache, we can't
Alex,
You get me right. DEFAULT -> LOG_ONLY doesn't introduce any dramatic
changes when comparing 2.3 to 2.4 - Ignite was unsafe out of the box in
2.3, and it is unsafe in 2.4 as well.
The very problem is that we claim ourselves to be ACID, while in reality we
are only "AI" out of the box, becaus
Hi Folks,
We have performance suggestions logged during Ignite start. Can we create
data safety suggestions and list all these options during startup?
Arguments about Ignite is distributed and may have backup for protection
make sence.
Who can provide reference to test of such or similar scenari
Taras Ledkov created IGNITE-7745:
Summary: JDBC: Add a note about SSL connection to docs
Key: IGNITE-7745
URL: https://issues.apache.org/jira/browse/IGNITE-7745
Project: Ignite
Issue Type: Ta
In terms of 'safety', Ignite default settings are far beyond optimal. For
in-memory mode, we have 0 backups by default, which means partition loss in
a case of node failure, we have readFromBackup=true and PRIMARY_SYNC by
default which effectively cancels linearizability property for cache
updates,
Stéphane Thibaud created IGNITE-7744:
Summary: OPTIONAL_LIBS environment variable is not picked up
Key: IGNITE-7744
URL: https://issues.apache.org/jira/browse/IGNITE-7744
Project: Ignite
Hi Pavel,
About queue: all these builds were manually triggered by me. It is like
experiment under MakeTeamCityGreenAgain. I am trying to accumulate
statistics about failing tests in master. Feel free to reoder your build to
top.
Statistic is necessary to find out how much tests are actually fail
Igniters,
Currently we have a TeamCity trigger only on Run All aggregating project:
https://ci.ignite.apache.org/admin/editTriggers.html?id=buildType:IgniteTests24Java8_RunAll
Each change triggers it's own full run. If new changes are added while some
builds are queued,
these changes are not pick
Works are completed.
Server Teamcity is working.
Sorry for delay.
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
