This ticket is very important too, as for me [1] Anton Kalashnikov, what do you
think ?
[1] https://issues.apache.org/jira/browse/IGNITE-12801
>Folks,
>
>I'd like to add ticket IGNITE-12805 "NullPointerException on node restart
>when 3rd party persistence and Ignite native persistence are
Raymond,
I've seen this behaviour before, it occurs on massive data loading to a
cluster with a small data region. It's not reproducible with data regions
with normal sizes, I think that this is the reason why this issue is not
fixed yet.
Best Regards,
Evgenii
ср, 8 апр. 2020 г. в 04:23,
I would like to understand your solution deeper. Hope, that my questions
are interesting not only for me:
- What about primary/backup node data consistency. I found, that [1]
Cassandra uses eventually consistent backups, so some backup data could
miss from snapshot. If I apply snapshot,
Igniters,
There was a private discussion between Nikolay Izhikov, Andrey Gura, Alex
Goncharuk and I some time ago where we attempted to outline a list of tasks
to complete before announcing the feature in the GA state (removing the
experimental flag from the new APIs and deprecating the legacy
Denis A. Magda created IGNITE-12880:
---
Summary: IllegalArgumentException on activation of LogExporterSpi
Key: IGNITE-12880
URL: https://issues.apache.org/jira/browse/IGNITE-12880
Project: Ignite
Igniters,
Let's remove "This operating system has been tested less rigorously"
diagnostic [1] [2].
It does not make sense:
* All Linux and macOS versions are considered the same
* Windows versions are differentiated
* Windows 10 and all Windows Servers are considered badly tested
None of that is
Alright folks, we've approached the end of the migration process and here
is an updated instruction for those who will push changes:
https://cwiki.apache.org/confluence/display/IGNITE/Website+Development
-
Denis
On Mon, Apr 6, 2020 at 5:05 PM Denis Magda wrote:
> A minor correction, that's
Folks,
I'd like to add ticket IGNITE-12805 "NullPointerException on node restart
when 3rd party persistence and Ignite native persistence are used" to
ignite-2.8.1 scope.
[1] https://issues.apache.org/jira/browse/IGNITE-12805
Thanks,
S.
вт, 7 апр. 2020 г. в 19:57, Ilya Kasnacheev :
> Hello!
Andrey,
Thanks for your questions, I've also clarified some details on the
IEP-43 [1] page according to them.
> Does snapshot contain only primary data or backup partitions or both?
A snapshot contains a full copy of persistence data on each local
node. This means all primary, backup
PetrovMikhail created IGNITE-12879:
--
Summary: Change DiscoveryHook methods naming.
Key: IGNITE-12879
URL: https://issues.apache.org/jira/browse/IGNITE-12879
Project: Ignite
Issue Type:
Hi, Maxim!
It is very useful feature, great job!
But could you explain me some aspects?
- Does snapshot contain only primary data or backup partitions or both?
- Could I create snapshot from m-node cluster and apply it to n-node
cluster (n<>m)?
- Should data node has extra space on
Sergey Chugunov created IGNITE-12878:
Summary: Improve logging for async writing of Binary Metadata
Key: IGNITE-12878
URL: https://issues.apache.org/jira/browse/IGNITE-12878
Project: Ignite
Ivan Bessonov created IGNITE-12877:
--
Summary: "restorePartitionStates" always logs all meta pages into
WAL
Key: IGNITE-12877
URL: https://issues.apache.org/jira/browse/IGNITE-12877
Project: Ignite
Sergey Chugunov created IGNITE-12876:
Summary: Test to cover deadlock fix between checkpoint, entry
update and ttl-cleanup threads
Key: IGNITE-12876
URL: https://issues.apache.org/jira/browse/IGNITE-12876
Stephen,
Thanks for the hint.
Vladimir,
Great idea! Let me know if any help needed.
On Wed, Apr 8, 2020 at 2:19 PM Vladimir Steshin wrote:
> Hi everyone.
>
> I think we should check behavior of failure detection with tests or find
> them if already written. I’ll research this question and rise
Evgenii,
Have you had a chance to look into the reproducer?
Thanks,
Raymond.
On Fri, Mar 6, 2020 at 2:51 PM Raymond Wilson
wrote:
> Evgenii,
>
> I have created a reproducer that triggers the error with the buffer size
> set to 64Mb. The program.cs/csproj and log for the run that triggered the
Hi everyone.
I think we should check behavior of failure detection with tests or find
them if already written. I’ll research this question and rise a ticket
if a reproducer appears.
08.04.2020 12:19, Stephen Darlington пишет:
Yes. Nodes are always chatting to each another even if there
Ivan Bessonov created IGNITE-12875:
--
Summary: Implement "EVT_CLUSTER_STATE_CHANGE_STARTED" event
Key: IGNITE-12875
URL: https://issues.apache.org/jira/browse/IGNITE-12875
Project: Ignite
That's cool.
I'm waiting for this thing.
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Yes. Nodes are always chatting to each another even if there are no requests
coming In.
Here’s the status message:
Ivan Bessonov created IGNITE-12874:
--
Summary: Possible NPE in
GridDiscoveryManager#cacheGroupAffinityNode
Key: IGNITE-12874
URL: https://issues.apache.org/jira/browse/IGNITE-12874
Project: Ignite
It seems you're talking about Failure Detection (Timeouts).
Will it detect node failure on still cluster?
On Wed, Apr 8, 2020 at 11:52 AM Stephen Darlington <
stephen.darling...@gridgain.com> wrote:
> The configuration parameters that I’m aware of are here:
>
>
>
The configuration parameters that I’m aware of are here:
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/discovery/tcp/TcpDiscoverySpi.html
Other people would be better placed to discuss the internals.
Regards.
Stephen
> On 8 Apr 2020, at 09:32, Anton Vinogradov wrote:
Stephen,
> Nodes check on their neighbours and notify the remaining nodes if one
disappears.
Could you explain how this works in detail?
How can I set/change check frequency?
On Wed, Apr 8, 2020 at 11:13 AM Stephen Darlington <
stephen.darling...@gridgain.com> wrote:
> This is one of the
This is one of the functions of the DiscoverySPI. Nodes check on their
neighbours and notify the remaining nodes if one disappears. When the topology
changes, it triggers a rebalance, which relocates primary partitions to live
nodes. This is entirely transparent to clients.
It gets more
Igniters,
Do we have some feature allows to check nodes aliveness on a regular basis?
Scenario:
Precondition
The cluster has no load but some node's JVM crashed.
Expected actual
The user performs an operation (eg. cache put) related to this node (via
another node) and waits for some timeout
Kirill Tkalenko created IGNITE-12873:
Summary: Hosts names resolution takes place even if all nodes are
configured via ip addresses
Key: IGNITE-12873
URL: https://issues.apache.org/jira/browse/IGNITE-12873
27 matches
Mail list logo
