This is my fault, introduced within
https://issues.apache.org/jira/browse/IGNITE-10715
I have no idea why it had not been failed during testing on TC.
I will prepare the fix quickly.
On Tue, Dec 25, 2018 at 2:37 AM wrote:
>
> Hi Igniters,
>
> I've detected some new issue on TeamCity to be hand
Sergey Chugunov created IGNITE-10809:
Summary:
IgniteClusterActivateDeactivateTestWithPersistence.testActivateFailover3 fails
in master
Key: IGNITE-10809
URL: https://issues.apache.org/jira/browse/IGNITE-1080
The failure has been introduced within task:
https://issues.apache.org/jira/browse/IGNITE-10671 Double
initialization of segmentAware and FileArchiver lead to race breaking
file compression.
The cause is a missed '@Test' annotation.
Here is the patch to fix [1], TC test is green [2].
[1] https:/
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 finalize
>
> In my case, values are immutable - I never change them, I just add new
> entry for newer versions. Does it mean that I won't have any duplicates
> between the initial query and listener entries when using continuous
> queries on caches supporting MVCC?
I'm afraid there still might be a race.
Yuri, Vladimir,
How expensive will it be to have the history enabled by default? For
instance, let's take the running queries mechanics as an example, what is
the performance impact the did?
As for the running queries, Yuri, if it's completed please send a summary
to the relevant discussion expla
Gert, All,
That's not a peer-class-loading issue but rather the binary objects
limitation. It's impossible to change the *type* of an object field. You
can add new fields or remove existing ones. The same limitation applies to
SQL - now way to change the type in runtime. That latter should be
addr
Hello!
As far as my understanding goes it checks some basic invariants of events()
API - e.g. that it does not crash if you try to de-register inexistent
listener or that it returns a valid handle if you register a new one.
Regards,
--
Ilya Kasnacheev
пн, 24 дек. 2018 г. в 20:14, Chandranana N
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 finalize
Hello, Igniters.
Please, let us know, if someone want to do additional review of this PR.
В Пн, 24/12/2018 в 20:23 +0300, Vyacheslav Daradur пишет:
> Igniters, especially future reviewers,
>
> Discovery listener registered by 'IgniteServiceProcessor' become
> implemented 'HighPriorityListener',
Igniters, especially future reviewers,
Discovery listener registered by 'IgniteServiceProcessor' become
implemented 'HighPriorityListener', seems it's best lock-free
solutions discussed during the review. This change is covered by
`ServiceDeploymentDiscoveryListenerNotificationOrderTest` which sho
Hi Team,
I have recently started working with Apache Ignite. Build on x86 Ubuntu 16.04
is complete. I wanted some information on the tests I am running.
Could you please give some information on what the test does -
GridEventConsumeSelfTest#testApi, I want to understand the functionality of the
Stanislav Lukyanov created IGNITE-10808:
---
Summary: Discovery message queue may build up with
TcpDiscoveryMetricsUpdateMessage
Key: IGNITE-10808
URL: https://issues.apache.org/jira/browse/IGNITE-10808
HI, Igniters!
I've updated and rebased implementation to master branch and made some
fixes.
Also I have a question regarding current implementation.
As I found Cron4J source code this implementation checks schedule every
minute (seconds not supported) but spawns a thread for every task which
sche
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 finalize
Hi,
Mentioned javadoc.css references to some image resources. They present
for 2.3.0 release [1]. But similar url returns 404 for 2.7.0 [2]. Who
knows how to upload resources?
[1] https://ignite.apache.org/releases/2.3.0/javadoc/resources
[2] https://ignite.apache.org/releases/2.7.0/javadoc/resou
Stanislav, thank you for the notes, most of them have been resolved. I
answered on GitHub.
On Sun, Dec 23, 2018 at 9:34 PM Stanislav Lukyanov
wrote:
>
> I’ve done a quick superficial review. Didn’t look at the tests, didn’t dive
> into the design, etc, just the code.
> I’ve left some comments –
Igor, thanks for your feedback! Let's do according to your proposal.
пн, 24 дек. 2018 г. в 14:57, Seliverstov Igor :
>
> Ivan,
>
> We have to design configuration carefully.
> There are possible issues with compatibility and this API is public, it
> might be difficult to redesign it after while.
>
Ivan Pavlukhin created IGNITE-10807:
---
Summary: Support long-running tx rollback on PME
Key: IGNITE-10807
URL: https://issues.apache.org/jira/browse/IGNITE-10807
Project: Ignite
Issue Type:
Namrata Bhave created IGNITE-10806:
--
Summary: Test failure on Big Endian
Key: IGNITE-10806
URL: https://issues.apache.org/jira/browse/IGNITE-10806
Project: Ignite
Issue Type: Bug
Affects
Folks,
The important thing here is that 99% of "final static" ip-finders were
removed. (~800 pcs.)
Non-static, mostly, kept as is since removal may or cause a test failure.
(~130 pcs.)
In case someone interested in the continuation of cleanup, please feel free
to create an issue and provide PR, I
Ryabov Dmitrii created IGNITE-10805:
---
Summary: [TC Bot] Gather info from investigations for page with
muted tests
Key: IGNITE-10805
URL: https://issues.apache.org/jira/browse/IGNITE-10805
Project: I
The second step [2] "removing related boilerplate in tests" - has been
done. It is expected that a bit memory will be released at tests TC
agents, which could not be cleaned by GC because of static final
fields.
Guys, please, do not generate a new one )
[1] https://issues.apache.org/jira/browse/I
Ivan,
We have to design configuration carefully.
There are possible issues with compatibility and this API is public, it
might be difficult to redesign it after while.
Since there is a ticket about MVCC related configuration parts [1] (TxLog
memory region/size, vacuum thread count and intervals,
Aleksey Zinoviev created IGNITE-10804:
-
Summary: [ML] Add ability to load LinReg model from Spark to
Ignite via PMML
Key: IGNITE-10804
URL: https://issues.apache.org/jira/browse/IGNITE-10804
Proje
Aleksey Zinoviev created IGNITE-10803:
-
Summary: [ML] Add prototype LinearRegression loading from PMML
format
Key: IGNITE-10803
URL: https://issues.apache.org/jira/browse/IGNITE-10803
Project: Ign
Alex Volkov created IGNITE-10802:
Summary: Documentation for option
IGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE
Key: IGNITE-10802
URL: https://issues.apache.org/jira/browse/IGNITE-10802
Project: Ign
Sergey Antonov created IGNITE-10801:
---
Summary: Update H2 verstion to 1.4.198
Key: IGNITE-10801
URL: https://issues.apache.org/jira/browse/IGNITE-10801
Project: Ignite
Issue Type: Improvemen
Ilya Suntsov created IGNITE-10800:
-
Summary: Add wal_mode parameter to properties file
Key: IGNITE-10800
URL: https://issues.apache.org/jira/browse/IGNITE-10800
Project: Ignite
Issue Type: Bu
Pavel Kovalenko created IGNITE-10799:
Summary: Optimize affinity initialization/re-calculation
Key: IGNITE-10799
URL: https://issues.apache.org/jira/browse/IGNITE-10799
Project: Ignite
Is
Sergi Vladykin created IGNITE-10798:
---
Summary: Data page scan for ScanQuery, SqlQuery and SqlFieldsQuery
Key: IGNITE-10798
URL: https://issues.apache.org/jira/browse/IGNITE-10798
Project: Ignite
31 matches
Mail list logo
