Alexander Kalinin created IGNITE-8933:
-
Summary: Fix web-console tests CI because of package-lock
Key: IGNITE-8933
URL: https://issues.apache.org/jira/browse/IGNITE-8933
Project: Ignite
I
GitHub user daradurvs opened a pull request:
https://github.com/apache/ignite/pull/4307
IGNITE-8361 Use discovery messages for service deployment
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/daradurvs/ignite ignite-8361-rc
Al
Evgenii Zhuravlev created IGNITE-8934:
-
Summary: LongJVMPauseDetector prints error on thread interruption
when node stopping
Key: IGNITE-8934
URL: https://issues.apache.org/jira/browse/IGNITE-8934
Igniters,
I need help with TeamCity.
.NET Linux Tests [1] fail for a very weird reason:
Newtonsoft.Json.dll seems to be corrupted or empty " *Image is too small.*
".
I tried adding a step to clean NuGet caches, but it does not help.
On my Ubuntu box tests pass. And there were no changes to .NET l
GitHub user ezhuravl opened a pull request:
https://github.com/apache/ignite/pull/4308
IGNITE-8934 remove error message when LongJVMPauseDetector stops
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite
I can.
Can you prepare reproduce steps so that I’ll be able to pinpoint the problem
faster, please?
> On 5 Jul 2018, at 11:25, Pavel Tupitsyn wrote:
>
> Igniters,
>
> I need help with TeamCity.
> .NET Linux Tests [1] fail for a very weird reason:
> Newtonsoft.Json.dll seems to be corrupted
Guys,
Do we really need events for activation/deactivation? We already have a
ticket for implementation lifecycle events for it:
https://issues.apache.org/jira/browse/IGNITE-5427, won't it be enough?
Evgenii
2018-07-03 16:06 GMT+03:00 Ken Cheng :
> Hi dsetrakyan,
>
> I checked the source again
Ilya Kasnacheev created IGNITE-8935:
---
Summary: IgniteConfiguration dependents should have toString
Key: IGNITE-8935
URL: https://issues.apache.org/jira/browse/IGNITE-8935
Project: Ignite
Is
Maxim Muzafarov created IGNITE-8936:
---
Summary: Remove AffinityAssignment#clientEventChange as not used
Key: IGNITE-8936
URL: https://issues.apache.org/jira/browse/IGNITE-8936
Project: Ignite
Hello everyone,
Suppose clientEventChange method is useless and have confusing name.
I'm suggesting to remove it as not used. I've filed issue for it:
https://issues.apache.org/jira/browse/IGNITE-8936
чт, 28 июн. 2018 г. в 16:53, Maxim Muzafarov :
> Hi Igniters,
>
> Recently I've faced with A
Ilya Kasnacheev created IGNITE-8937:
---
Summary: JVM Crash in C++ suites on Windows/Java 8 (in PageIO)
Key: IGNITE-8937
URL: https://issues.apache.org/jira/browse/IGNITE-8937
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4244
---
Andrey Gura created IGNITE-8938:
---
Summary: file-decompressor thread termination should be handled
with Failure handler
Key: IGNITE-8938
URL: https://issues.apache.org/jira/browse/IGNITE-8938
Project: Ig
Evgenii Zagumennov created IGNITE-8939:
--
Summary: Error in binary meta data after RESTORE with
wal_compaction
Key: IGNITE-8939
URL: https://issues.apache.org/jira/browse/IGNITE-8939
Project: Igni
Anton Kalashnikov created IGNITE-8940:
-
Summary: Activation job
hangs(IgniteChangeGlobalStateTest#testFailGetLock)
Key: IGNITE-8940
URL: https://issues.apache.org/jira/browse/IGNITE-8940
Project:
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4309
IGNITE-8940 force fail of testFailGetLock
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8940
Alternatively you
I guess just activating the cluster would add all the existing nodes
to the baseline topology?
Exactly. Persistent cluster can't exist in active state without baseline
topology. First activation will establish BLT from current set of server
nodes.
Best Regards,
Ivan Rakov
On 04.07.2018 1:55,
GitHub user voipp opened a pull request:
https://github.com/apache/ignite/pull/4310
IGNITE-8570 Create lighter version of GridStringLogger
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/voipp/ignite IGNITE-8570
Alternatively yo
GitHub user vldpyatkov opened a pull request:
https://github.com/apache/ignite/pull/4311
IGNITE-8754
Node outside of baseline does not start when service configured
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-i
GitHub user aealeksandrov opened a pull request:
https://github.com/apache/ignite/pull/4312
Ignite 2.4.6.b2
PR created for team city test runs. Please don't merge.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ig
GitHub user NSAmelchev opened a pull request:
https://github.com/apache/ignite/pull/4313
IGNITE-8714
For IGNITE-8714.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/NSAmelchev/ignite ignite-8714
Alternatively you can review and
GitHub user 1vanan opened a pull request:
https://github.com/apache/ignite/pull/4314
IGNITE-8619 Remote node could not start in ssh connection
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/1vanan/ignite IGNITE-8619
Alternative
Mikhail Cherkasov created IGNITE-8941:
-
Summary: BinaryInvalidTypeException is thrown on invoke
Key: IGNITE-8941
URL: https://issues.apache.org/jira/browse/IGNITE-8941
Project: Ignite
Iss
Hi igniters!
Following our discussions about emergency releases I see that here might
be applied new way for doing releases. Like it was for Linux or like it
is for Ubuntu. I mean do interleaving releases: first is experimental
with newest features and second - with bug fixes ONLY.
For examp
Hi Dmitriy,
AFAIK we have an idea to introduce maintenance releases for Ignite. E.g.
2.6.0 - features, 2.6.1+ - stabilization.
This seems to be more standard and flexible approach.
чт, 5 июля 2018 г. в 17:39, Dmitry Karachentsev :
> Hi igniters!
>
> Following our discussions about emergency rel
Stan,
What is the purpose of clientFailureDetectionTimeout? Why can't we just
always use failureDetectionTimeout? Is there any difference between these
two timeouts?
-Val
On Wed, Jul 4, 2018 at 7:00 AM Stanislav Lukyanov
wrote:
> Hi,
>
> I’ve updated the proposed documentation update with a
Pavel,
Design you described is almost precisely what IGFS does. It has a cache for
metadata, split binary data in chunks with intelligent affinity routing. In
addition we have map-reduce feature on top of it and integration with
underlying file system with optional caching. Data can be accessed in
Alexei Scherbakov created IGNITE-8942:
-
Summary: In some cases grid cannot be deactivated because of
hanging CQ internal cleanup.
Key: IGNITE-8942
URL: https://issues.apache.org/jira/browse/IGNITE-8942
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/4315
ignite-8905 with merged master
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8905-mm
Alternativel
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/4316
IGNITE-8938 Failure handling for file-decompressor thread added
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite ignite-893
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/4317
IGNITE-8766 - TcpDiscoverySpi: discovery threads naming
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-876
Andrew Medvedev created IGNITE-8943:
---
Summary: Deactivation in large cluster hangs during rebalance
Key: IGNITE-8943
URL: https://issues.apache.org/jira/browse/IGNITE-8943
Project: Ignite
I
Github user dkarachentsev closed the pull request at:
https://github.com/apache/ignite/pull/4299
---
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4318
IGNITE-8935 toString() or exclusion for most classes accessible from
IgniteConfiguration
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridga
Dmitry Karachentsev created IGNITE-8944:
---
Summary: TcpDiscoverySpi: set connection check frequency to fixed
value
Key: IGNITE-8944
URL: https://issues.apache.org/jira/browse/IGNITE-8944
Project:
Github user agura closed the pull request at:
https://github.com/apache/ignite/pull/4306
---
Github user agura closed the pull request at:
https://github.com/apache/ignite/pull/4204
---
Thanks Ivan. I will fix the doc accordingly.
On Thu, Jul 5, 2018 at 5:31 AM, Ivan Rakov wrote:
> I guess just activating the cluster would add all the existing nodes to
> the baseline topology?
>
> Exactly. Persistent cluster can't exist in active state without baseline
> topology. First activat
Vladimir,
The key difference between BLOB storage and IGFS is that BLOB storage will
have persistent-based architecture with possibility to cache blocks in
offheap (using mmap, which is more simple, because we delegate it to OS
level)
, while IGFS has in-memory based architecture with possibility
Ivan Daschinskiy created IGNITE-8945:
Summary: Stored cache data files corruption when node stops
abruptly.
Key: IGNITE-8945
URL: https://issues.apache.org/jira/browse/IGNITE-8945
Project: Ignite
Pavel,
IGFS doesn't enforce you to have block in heap. What you suggest can be
achieved with IGFS as follows:
1) Disable caching, so data cache is not used ("PROXY" mode)
2) Implement IgniteFileSystem interface which operates on abstract streams
But the whole idea around mmap sounds like prematur
Vladimir,
I didn't say that it stores data in on-heap, I said that it performs a lot
of operations with byte[] arrays in on-heap as I see in , which will lead
to frequent GCs and unnecessary data copying.
"But the whole idea around mmap sounds like premature optimisation to me" -
this is not prema
On Thu, Jul 5, 2018 at 1:55 AM, Evgenii Zhuravlev
wrote:
> Guys,
>
> Do we really need events for activation/deactivation? We already have a
> ticket for implementation lifecycle events for it:
> https://issues.apache.org/jira/browse/IGNITE-5427, won't it be enough?
>
Hm... I think these two tic
Vladimir,
I just want to add to my words, that we can implement BLOB storage and
then, if community really wants it, we can adapt this storage to use as
underlying file system in IGFS. But IGFS shouldn't be entry point for BLOB
storage. I think this conclusion can satisfy both of us.
2018-07-06 0
Ivan Rakov created IGNITE-8946:
--
Summary: AssertionError can occur during reservation of WAL
history for historical rebalance
Key: IGNITE-8946
URL: https://issues.apache.org/jira/browse/IGNITE-8946
Proje
GitHub user ivandasch opened a pull request:
https://github.com/apache/ignite/pull/4319
IGNITE-8945: Add additional checks with informative error message
and implement more robust storedcachedata save.
You can merge this pull request into a Git repository by running:
$ git pull
I have triggered my tests many times on TeamCity. every time I get the same
result.
Platform .NET (Core Linux) pull/4300/head #1109 Exit code 1 (new)
https://ci.ignite.apache.org/viewLog.html?buildId=1460429&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunBasicTests.
I checked the
47 matches
Mail list logo
