kcheng.mvp created IGNITE-8956:
--
Summary: Javadoc
Warnings:core/src/main/java/org/apache/ignite/internal/processors/cache/WalStateManager.java:1271:
warning - @inheritDoc used but check() does not override or implement any
method.
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/4327
Ignite-8955
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8955-1
Alternatively you can review and apply
Igniters,
Please review my changes. That's a simple change, a setter method was added.
Thanks,
Amir
GitHub user amirakhmedov opened a pull request:
https://github.com/apache/ignite/pull/4326
IGNITE-8880: Add setIgnite() in SpringCacheManager and SpringTransactâ¦
â¦ionManager
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user ivandasch opened a pull request:
https://github.com/apache/ignite/pull/4325
IGNITE-8869: Exclude daemon's nodes from ExchangeLatch.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ivandasch/ignite ignite-8869-fix
What is the difference between a lifecycle even and regular events?
On Fri, Jul 6, 2018 at 12:25 AM, Evgenii Zhuravlev wrote:
> I've linked them as duplicates, however, one ticket suggests to add
> Lifecycle events, while another is for adding our simple events
> from EventType
>
> Evgenii
>
>
Can we print out the configuration to a separate file? Moreover, I think we
should also print out the configuration differences between nodes, whenever
new nodes join topology.
D.
On Fri, Jul 6, 2018 at 6:51 AM, Ilya Kasnacheev
wrote:
> Hello!
>
> I was working on
Eduard Shangareev created IGNITE-8955:
-
Summary: Checkpoint can't get write lock if massive eviction on
node start started
Key: IGNITE-8955
URL: https://issues.apache.org/jira/browse/IGNITE-8955
Stan,
Can you explain the semantics of both parameters? How do they behave when
set on client or on server?
-Val
On Fri, Jul 6, 2018 at 6:12 AM Stanislav Lukyanov
wrote:
> We could just use failureDetectionTimeout all the time I guess.
> The only benefit of clientFailureDetectionTimeout is
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4302
---
GitHub user glukos opened a pull request:
https://github.com/apache/ignite/pull/4324
IGNITE-8946 AssertionError can occur during release of WAL history thâ¦
â¦at was reserved for historical rebalance
You can merge this pull request into a Git repository by running:
$ git
Pavel,
The only newtonsoft.json found are
/usr/share/dotnet/sdk/NuGetFallbackFolder/newtonsoft.json (versions 9.0.1 and
10.0.1) and /usr/share/dotnet/store/x64/netcoreapp2.0/newtonsoft.json (version
10.0.1). There is nothing in .nuget/packages.
The sizes of corresponding Newtonsoft.Json.dll
Eventually, everything is green!
https://ci.ignite.apache.org/viewLog.html?buildId=1462771=buildResultsDiv=IgniteTests24Java8_RunBasicTests
thank you all very much!
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Sergey Kosarev created IGNITE-8954:
--
Summary: Rebalance has restarted fully after reassigning missing
partitions
Key: IGNITE-8954
URL: https://issues.apache.org/jira/browse/IGNITE-8954
Project:
GitHub user oleg-ostanin opened a pull request:
https://github.com/apache/ignite/pull/4323
Ignite 8322 fix
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8322-fix
Alternatively you can review and
Hi Dmitry,
I think maintenance release is fine only if they will include ONLY
fixes. This will allow to release more frequently, so we do not have to
wait when collect some number of fixes to make a next major version.
So each major release could be named as experimental, and maintenance -
Not really, extracting a method to a superinterface is a fully compatible
change.
There won’t be any compatibility issues because of this (disregarding possible
bugs, of course ;) ).
In any case, I’m not planning to fix it right away – this isn’t anywhere near
critical or urgent, obviously.
I
Hello!
I was working on https://issues.apache.org/jira/browse/IGNITE-8935 to avoid
default toString() implementations in classes reachable from
IgniteConfiguration, which we print on start-up.
I have discovered that by default we avoid printing arrays and collections.
We only print those when
Anton Kalashnikov created IGNITE-8953:
-
Summary: Test fail: Bind address already in
use(TcpDiscoverySpiFailureTimeoutSelfTest)
Key: IGNITE-8953
URL: https://issues.apache.org/jira/browse/IGNITE-8953
Hi Igniters,
here I will extremely appreciate vision from community members invoved into
release. What is simpler, support 2.7-EA- or 2.7.x?
Taking into account Teamcity state, it is quite honest to have experimental
releases to underline that
- a lot of new code introduced
- and probably new
Hi,
Is this question related to some contribution? If not, probably user@ list
is better place to ask, even if question is advanced. Community members
monitors user list, so even advanced question can find asnwer there.
Dev@ list is intended for discussions related to particular contributions,
As far as I understand we should to wait 3.0, shouldn't we?
пт, 6 июл. 2018 г. в 16:17, Stanislav Lukyanov :
> Hi Igniters,
>
> I’ve just created a ticket to move CacheStore::loadCache to a separate
> interface:
> https://issues.apache.org/jira/browse/IGNITE-8952
> In short, this is to provide a
Hi Igniters,
I’ve just created a ticket to move CacheStore::loadCache to a separate
interface:
https://issues.apache.org/jira/browse/IGNITE-8952
In short, this is to provide a way to only implement loadCache without messing
with other methods CacheStore implements. More details are in the JIRA.
Guys, I created ticket for config params validation -
https://issues.apache.org/jira/browse/IGNITE-8951. Feel free to comment.
Yakov Zhdanov
www.gridgain.com
2018-07-04 10:51 GMT+03:00 Andrew Medvedev :
> Hi Nikolay
>
> No, we have been beaten by
>
We could just use failureDetectionTimeout all the time I guess.
The only benefit of clientFailureDetectionTimeout is that it may allow clients
to be slower/on a slower network than servers.
Do you think it isn’t worth to have a separate setting just for that?
Thanks,
Stan
From: Valentin
Stanislav Lukyanov created IGNITE-8952:
--
Summary: Move CacheStore::loadCache to a separate interface
Key: IGNITE-8952
URL: https://issues.apache.org/jira/browse/IGNITE-8952
Project: Ignite
Hi Maxim,
Thank you for your efforts to finding this out. I also didn't find any
usages, so I agree here.
I'm going to commit this by lazy consensus if no-one objects within the
next three days.
Sincerely,
Dmitriy Pavlov
чт, 5 июл. 2018 г. в 12:56, Maxim Muzafarov :
> Hello everyone,
>
>
Yakov Zhdanov created IGNITE-8951:
-
Summary: Need to validate nodes configuration across cluster and
warn on different parameters value
Key: IGNITE-8951
URL: https://issues.apache.org/jira/browse/IGNITE-8951
Igniters,
Ignite version still 2.6.0-SNAPSHOT at master,
It should be changed to 2.7.0-SNAPSHOT since we relocated 2.6 to a special
branch.
Some issues affecting backward compatibility can not be merged while
version not incremented.
ср, 4 июл. 2018 г. в 20:59, Andrey Gura :
> Igniters,
>
>
GitHub user zstan opened a pull request:
https://github.com/apache/ignite/pull/4322
IGNITE-8950 More informative file validation check message
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8950
No.
I am investigating your case in dedicated agent.
> On 6 Jul 2018, at 15:43, Pavel Tupitsyn wrote:
>
> I see that some .NET Linux builds are now green.
> Petr, have you done anything other than reboot?
>
> On Fri, Jul 6, 2018 at 3:05 PM Petr Ivanov wrote:
>
>> Agents rebooted
>>
>>
I see that some .NET Linux builds are now green.
Petr, have you done anything other than reboot?
On Fri, Jul 6, 2018 at 3:05 PM Petr Ivanov wrote:
> Agents rebooted
>
>
>
> > On 6 Jul 2018, at 14:09, kcheng.mvp wrote:
> >
> > In the console of TeamCity, I noticed some message
> >
> >
> > Some
Stanilovsky Evgeny created IGNITE-8950:
--
Summary: Need to have more informative output info while database
files check operation.
Key: IGNITE-8950
URL: https://issues.apache.org/jira/browse/IGNITE-8950
Alexei Scherbakov created IGNITE-8949:
-
Summary: Unexpected exception after node restart during rebalance.
Key: IGNITE-8949
URL: https://issues.apache.org/jira/browse/IGNITE-8949
Project: Ignite
Ilya Kasnacheev created IGNITE-8948:
---
Summary: Allow checking of LOGGING status via SQL/JDBC
Key: IGNITE-8948
URL: https://issues.apache.org/jira/browse/IGNITE-8948
Project: Ignite
Issue
Agents rebooted
> On 6 Jul 2018, at 14:09, kcheng.mvp wrote:
>
> In the console of TeamCity, I noticed some message
>
>
> Some dependencies of this build are hanging: … Platform .NET (Core Linux),
> build #1094
>
>
> it's hanging about 20 hours. is there anyway to cancel or stop it?
>
>
In the console of TeamCity, I noticed some message
Some dependencies of this build are hanging: … Platform .NET (Core Linux),
build #1094
it's hanging about 20 hours. is there anyway to cancel or stop it?
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
GitHub user ivandasch opened a pull request:
https://github.com/apache/ignite/pull/4321
IGNITE-7366. Code review reaction
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7366
Alternatively you can
Petr,
- Get the sources
- cd modules/platforms/dotnet/Apache.Ignite.Core.Tests.DotNetCore
- dotnet build
You should get a warning "warning MSB3246: Resolved file has a bad image,
no metadata, or is otherwise inaccessible. Image is too small."
If you do, go ahead:
- cd
Hi Pavel,
Sure, I didn't understood that problem is the same with already discussed.
пт, 6 июл. 2018 г. в 12:01, Pavel Tupitsyn :
> Dmitry, see my reply above. I will provide steps to Petr in that other
> thread.
>
> On Fri, Jul 6, 2018 at 12:00 PM Dmitry Pavlov
> wrote:
>
> > Hi,
> >
> >
Dmitry, see my reply above. I will provide steps to Petr in that other
thread.
On Fri, Jul 6, 2018 at 12:00 PM Dmitry Pavlov wrote:
> Hi,
>
> Unfortunately this problem also occurs in master, so for now everything we
> can do now it is to Ignore it for PR and handle it as part of Make TeamCity
Hi,
Unfortunately this problem also occurs in master, so for now everything we
can do now it is to Ignore it for PR and handle it as part of Make TeamCity
Green Again activity.
Igniters, who can assist in fixing this issue:
Testhost process exited with error: Unhandled Exception:
Yes, this is being discussed in [1]
[1]
http://apache-ignite-developers.2346864.n4.nabble.com/NET-tests-fail-on-Linux-need-help-with-TeamCity-td32235.html
On Fri, Jul 6, 2018 at 8:52 AM kcheng.mvp wrote:
> I have triggered my tests many times on TeamCity. every time I get the same
> result.
>
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/4320
IGNITE-8944 - TcpDiscoverySpi: set connection check frequency to fixeâ¦
â¦d value
You can merge this pull request into a Git repository by running:
$ git pull
Pavel,
I do not think it is a good idea to delay discussions and decisions.
Because it puts your efforts at risk being not accepted by community in the
end. Our ultimate goal is not having as much features as possible, but to
have a consistent product which is easy to understand and use. Having
I've linked them as duplicates, however, one ticket suggests to add
Lifecycle events, while another is for adding our simple events
from EventType
Evgenii
2018-07-06 1:10 GMT+03:00 Dmitriy Setrakyan :
> On Thu, Jul 5, 2018 at 1:55 AM, Evgenii Zhuravlev <
> e.zhuravlev...@gmail.com>
> wrote:
>
>
Alexey Kuznetsov created IGNITE-8947:
Summary: Web Console: minor regression on Queries screen
Key: IGNITE-8947
URL: https://issues.apache.org/jira/browse/IGNITE-8947
Project: Ignite
47 matches
Mail list logo
