I'll take a look.
ср, 22 июл. 2020 г. в 06:29, :
> Hi Igniters,
>
> I've detected some new issue on TeamCity to be handled. You are more than
> welcomed to help.
>
> If your changes can lead to this failure(s): We're grateful that you were
> a volunteer to make the contribution to this
Vladimir Steshin created IGNITE-13282:
-
Summary: Fix
TcpDiscoveryCoordinatorFailureTest.testClusterFailedNewCoordinatorInitialized()
Key: IGNITE-13282
URL: https://issues.apache.org/jira/browse/IGNITE-13282
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
Hi Evgeniy,
Can you please confirm in your configuration you have this example config
file.
https://github.com/apache/ignite/blob/master/examples/config/example-cache.xml#L26-L32
This has instructions on default cache config.
My understanding is when node startup then the default cache should
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
Stanilovsky Evgeny created IGNITE-13281:
---
Summary: Test failed:
GridIoManagerFileTransmissionSelfTest#testChunkHandlerInitSizeFail
Key: IGNITE-13281
URL: https://issues.apache.org/jira/browse/IGNITE-13281
Alex,
I think it makes sense to enable distribution of these events by default,
since they won't introduce any performance impact, and they may be pretty
useful for the application lifecycle management.
The following events also make sense to be enabled by default:
- EVT_BASELINE_CHANGED
Discussed privately with Max.
Discussion results provided at the slack channel [1].
[1] https://the-asf.slack.com/archives/C016F4PS8KV/p1595336751234500
On Wed, Jul 15, 2020 at 3:59 PM Max Shonichev wrote:
> Anton, Nikolay,
>
> I want to share some more findings about ducktests I've stubmled
Alexey,
Thank you for explanation. I feel that I miss a couple bits to
understand the picture fully. I am thinking about a case which I tend
to call a Memcached use-case. There is a cache over underlying storage
with read-through and expiration and without any rebalancing at all.
When new nodes
Ivan,
In my understanding this mode does not work at all even in the presence of
ForceKeysRequest which is now supposed to fetch values from peers in case
of a miss. In this mode we 1) move partitions to OWNING state
unconditionally, and 2) choose an arbitrary OWNING node for force keys
request.
Stanilovsky Evgeny created IGNITE-13280:
---
Summary: Improper index usage, fields enumeration not used with pk
index creation.
Key: IGNITE-13280
URL: https://issues.apache.org/jira/browse/IGNITE-13280
Keshava Munegowda created IGNITE-13279:
--
Summary: Ignition.start failing with error
java.lang.IllegalStateException: Failed to parse version: -1595322995-
Key: IGNITE-13279
URL:
Stanilovsky Evgeny created IGNITE-13278:
---
Summary: Forgotten logger isInfoEnabled check.
Key: IGNITE-13278
URL: https://issues.apache.org/jira/browse/IGNITE-13278
Project: Ignite
Issue
Igniters,
There are 2 events in Ignite (EVT_CLUSTER_ACTIVATED
and EVT_CLUSTER_DEACTIVATED) that are only listened to by the coordinator.
To listen to them by other nodes, they must be included in
IgniteConfiguration.
There are also discovery events that are listened to by all nodes.
Both
Igniters,
Igor raised an interesting point in the PR:
Should we limit the number of Continuous Queries together with other queries
according to ClientConnectorConfiguration.maxOpenCursorsPerConn?
Or should we have a separate limit?
Technically, Ignite returns a QueryCursor, but it is very
15 matches
Mail list logo
