Hello everybody
Our company has lots of nodes in cluster, and we have seen some
problems with inconsistent settings on nodes clusterwide. To help us
with this, we made an utility to check consistency of settings on
running cluster, but it is a hack, better ways seems to be settings
validation by
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4284
---
Roman Guseinov created IGNITE-8923:
--
Summary: Add step-by-step guide - Google Cloud Engine Deployment
(Kubernetes)
Key: IGNITE-8923
URL: https://issues.apache.org/jira/browse/IGNITE-8923
Project:
On Mon, Jul 2, 2018 at 5:20 PM, John Wilson wrote:
> Regarding 1. I'm referring to the documentation here,
> https://apacheignite.readme.io/docs/topology-validation, which states
> "*Topology
> validator is used to verify that cluster topology is valid for further
> cache operations*." and "*If
Hi Ivan,
I have fixed and rephrased the section -
https://apacheignite.readme.io/v2.5/docs/baseline-topology#section-cluster-activation
However, I have a question regarding setting the baseline topology when
activating the cluster for the first time. In the web console, when we
activate the
I've tried to execute exactly the same code, it resulted with
class org.apache.ignite.IgniteException: Changing BaselineTopology on
inactive cluster is not allowed.
Basically, the code snippet is in "Setting the Topology From Code"
section, so we can make it correct by just removing
Prachi,
I do remember that that code, Ivan is referring to, worked fine for you.
Please double check. Probably you need to add "ignite.cluster.activate()"
to the code snippet.
--
Denis
On Tue, Jul 3, 2018 at 12:19 PM Ivan Rakov wrote:
> Igniters,
>
> Seems like we have an inconsistency in our
Igniters,
Seems like we have an inconsistency in our Baseline Topology
documentation:
https://apacheignite.readme.io/docs/baseline-topology#section-setting-the-topology-from-code
Java developers can use the IgniteCluster interface to initialize the
very first baseline topology or to adjust
Hi,
I was reading this documentation,
https://www.gridgain.com/resources/blog/apache-ignite-transactions-architecture-concurrency-modes-and-isolation-levels,
to understand the difference between Optimistic mode with Serializable vs
read_committed. The only difference I see from the explanation
Denis Mekhanikov created IGNITE-8922:
Summary: Discovery message delivery guarantee can be violated
Key: IGNITE-8922
URL: https://issues.apache.org/jira/browse/IGNITE-8922
Project: Ignite
Alexei Scherbakov created IGNITE-8921:
-
Summary: Add control.sh --cache affinity command to output current
and ideal assignment and optionally show diff between them
Key: IGNITE-8921
URL:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4285
---
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4296
IGNITE-8564 Clear affinity mapping cache when client node is disconnected.
You can merge this pull request into a Git repository by running:
$ git pull
Ivan Daschinskiy created IGNITE-8920:
Summary: Node should be failed when during tx finish indices are
corrupted.
Key: IGNITE-8920
URL: https://issues.apache.org/jira/browse/IGNITE-8920
Project:
Ivan Fedotov created IGNITE-8919:
Summary: Wrong documentation of exec methods in
StartNodeCallableImpl class
Key: IGNITE-8919
URL: https://issues.apache.org/jira/browse/IGNITE-8919
Project: Ignite
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4295
Preliminary Binary Object compression.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-compress
Alternatively
Hi dsetrakyan,
I checked the source again and found there is a customized Event sent out
with below code
org.apache.ignite.internal.processors.cluster.GridClusterSta
teProcessor#changeGlobalState0
I am not sure what you are referencing is this part? or still we need a
dedicated event for
Hi dsetrakyan,
I checked the source again and found there is a customized Event sent out
with below code
org.apache.ignite.internal.processors.cluster.GridClusterSta
teProcessor#changeGlobalState0
I am not sure what you are referencing is this part? or still we need a
dedicated event for
GitHub user x-kreator opened a pull request:
https://github.com/apache/ignite/pull/4294
Ignite 8910
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/x-kreator/ignite ignite-8910
Alternatively you can review and apply these
Sergey Kozlov created IGNITE-8918:
-
Summary: Redis examples don't work
Key: IGNITE-8918
URL: https://issues.apache.org/jira/browse/IGNITE-8918
Project: Ignite
Issue Type: Bug
Denis Mekhanikov created IGNITE-8917:
Summary: IgniteOutOfMemory when performing putAll with configured
pageEvictionMode
Key: IGNITE-8917
URL: https://issues.apache.org/jira/browse/IGNITE-8917
GitHub user avplatonov opened a pull request:
https://github.com/apache/ignite/pull/4293
Using vectors in featureExtractor
Refactoring for uniform interface of FeatureExtractor in trainer and model
You can merge this pull request into a Git repository by running:
$ git pull
Vica Abramova created IGNITE-8916:
-
Summary: Web Console: Replace font-awesome icons
Key: IGNITE-8916
URL: https://issues.apache.org/jira/browse/IGNITE-8916
Project: Ignite
Issue Type:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4282
---
Vyacheslav Daradur created IGNITE-8915:
--
Summary: NPE during executing local SqlQuery from client node
Key: IGNITE-8915
URL: https://issues.apache.org/jira/browse/IGNITE-8915
Project: Ignite
Roman Kondakov created IGNITE-8914:
--
Summary: SQL TX: Partition update counter fix.
Key: IGNITE-8914
URL: https://issues.apache.org/jira/browse/IGNITE-8914
Project: Ignite
Issue Type: Bug
Dmitriy, Yakov,
I've finalized design and prepared the solution [1].
1) Only events from GridNearTxLocal are registered now.
List of possible events:
public static final int[] EVTS_TX = {
EVT_TX_STARTED,
EVT_TX_COMMITTED,
EVT_TX_ROLLED_BACK,
EVT_TX_SUSPENDED,
Vladislav Pyatkov created IGNITE-8913:
-
Summary: Uninformative SQL query cancellation message
Key: IGNITE-8913
URL: https://issues.apache.org/jira/browse/IGNITE-8913
Project: Ignite
Dmitriy
You're right that that large objects storing should be optmized.
Let's assume the large object means the regular object having large fields
and such fileds won't be used for comparison thus we can do not restore the
BLOB fields in offheap page memory e.g for sql queries if select doesn't
Pavel Vinokurov created IGNITE-8912:
---
Summary: PartitionLossPolicy.READ_ONLY_SAFE does not detect
partition loss
Key: IGNITE-8912
URL: https://issues.apache.org/jira/browse/IGNITE-8912
Project:
30 matches
Mail list logo
