Great, thanks for letting me know.
вт, 10 июл. 2018 г. в 4:01, 李玉珏@163 <18624049...@163.com>:
> I have received the attachments.
>
> 在 2018/7/10 上午6:23, Prachi Garg 写道:
> > I already sent him the export, but the attachments were huge. I think
> > that's why the email reply was not received by the
Petr, looks like TC is back to normal.
I wonder what that was and whether NuGet cache cleanup step actually worked.
Thank you for your help, I will keep an eye on it.
On Fri, Jul 6, 2018 at 8:08 PM Petr Ivanov wrote:
> Pavel,
>
>
> The only newtonsoft.json found are
> /usr/share/dotnet/sdk/NuGe
Made comment there, c&p here as well
Is it going to be a preconfigured set of settings, or a whole range
of settings?
If latter :
1) Property names in CacheConfiguration do not always correspond to
getters (some follow different naming conventions, some are completely
different, as in memPlcNam
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4337
---
Anton Kalashnikov created IGNITE-8969:
-
Summary: Unable to await partitions release latch
Key: IGNITE-8969
URL: https://issues.apache.org/jira/browse/IGNITE-8969
Project: Ignite
Issue Typ
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4339
IGNITE-8969 Restore server latches if needed after node left the topoâ¦
â¦logy.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apach
GitHub user dgarus opened a pull request:
https://github.com/apache/ignite/pull/4340
IGNITE-8705. Added the way to clean metrics on cluster.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dgarus/ignite ignite-8705
Alternatively
Pavel Konstantinov created IGNITE-8970:
--
Summary: Web Console: Add the Clone action to a new configuration
UI
Key: IGNITE-8970
URL: https://issues.apache.org/jira/browse/IGNITE-8970
Project: Igni
Guys,
For your information: rebalanceThreadPoolSize validation is already
implemented and merged to master:
https://issues.apache.org/jira/browse/IGNITE-8904
You can overview the commit to see the approach. By the way, we already
validate some other parameters that can't differ among cluster n
Ivan, I would think of some test that will randomly generate configs for
nodes and run some logic.
--Yakov
.Hello Ivan,
I think it would be nice to add validation
DataRegionConfiguration#persistenceEnabled property. That property must be
the same across a cluster for the given data region.
Perhaps, different values of `initSize`, `maxSize` etc make sense in case
of a heterogeneous cluster, except `per
GitHub user Mmuzaf opened a pull request:
https://github.com/apache/ignite/pull/4341
Act deact to
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mmuzaf/ignite act-deact-to
Alternatively you can review and apply these changes as
Andrew Medvedev created IGNITE-8971:
---
Summary: GridRestProcessor should propagate error message
Key: IGNITE-8971
URL: https://issues.apache.org/jira/browse/IGNITE-8971
Project: Ignite
Issue
GitHub user andrewmed opened a pull request:
https://github.com/apache/ignite/pull/4342
IGNITE-8971 GridRestProcessor should propagate error message
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg
Igor Sapego created IGNITE-8972:
---
Summary: CPP Thin: Add thin client example
Key: IGNITE-8972
URL: https://issues.apache.org/jira/browse/IGNITE-8972
Project: Ignite
Issue Type: Improvement
Denis,
we have LongJVMPauseDetector. But it is Java thread that will be in
safe-point during stop-the-world pause and therefore will not make any
progress. So only external process can detect SW pause.
On Mon, Jul 2, 2018 at 10:34 PM Denis Magda wrote:
>
> Pavel,
>
> We already can monitor the st
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4293
---
Dmitriy Govorukhin created IGNITE-8973:
--
Summary: Need to support dump for idle_verify
Key: IGNITE-8973
URL: https://issues.apache.org/jira/browse/IGNITE-8973
Project: Ignite
Issue Type
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/4343
Ignite 2.4.6 p1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.6-p1
Alternatively you can review and apply
Roman Kondakov created IGNITE-8974:
--
Summary: MVCC TX: Vacuum cleanup version obtaining optimization.
Key: IGNITE-8974
URL: https://issues.apache.org/jira/browse/IGNITE-8974
Project: Ignite
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/4344
IGNITE-8900
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8900
Alternatively you can review and apply these c
Ivan Daschinskiy created IGNITE-8975:
Summary: Invalid initialization of compressed archived WAL segment
when WAL compression is switched off.
Key: IGNITE-8975
URL: https://issues.apache.org/jira/browse/IGNITE
Dmitriy Setrakyan created IGNITE-8976:
-
Summary: Add native persistence section to Key-Value data grid page
Key: IGNITE-8976
URL: https://issues.apache.org/jira/browse/IGNITE-8976
Project: Ignite
Dmitriy Setrakyan created IGNITE-8977:
-
Summary: Need to update distributed SQL page
Key: IGNITE-8977
URL: https://issues.apache.org/jira/browse/IGNITE-8977
Project: Ignite
Issue Type: Im
Github user alamar closed the pull request at:
https://github.com/apache/ignite/pull/3755
---
Github user alamar closed the pull request at:
https://github.com/apache/ignite/pull/3668
---
Github user alamar closed the pull request at:
https://github.com/apache/ignite/pull/2621
---
Github user alamar closed the pull request at:
https://github.com/apache/ignite/pull/3928
---
GitHub user ivandasch opened a pull request:
https://github.com/apache/ignite/pull/4345
IGNITE-8975: Correct handling compressed archived wal segment when coâ¦
â¦mpression is switched off.
You can merge this pull request into a Git repository by running:
$ git pull https://gi
Slava,
I agree. Different persistence enabled flag can cause unpleasant issues.
I've left a comment in IGNITE-8951.
Yakov,
Seems like I misunderstood the point of the discussion from the very
beginning. I thought that Andrew raised topic to discuss adding new
checks that will fail node join
GitHub user EdShangGG opened a pull request:
https://github.com/apache/ignite/pull/4346
Stockengine
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite stockengine
Alternatively you can review and apply these
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4347
IGNITE-8973 calculate partition hash and print into standard output
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite igni
Igniters,
We've uploaded a 2.6.0 release candidate to
https://dist.apache.org/repos/dist/dev/ignite/2.6.0-rc1/
Git tag name is 2.6.0-rc1.
This release includes the following changes:
Ignite:
* Fixed incorrect calculation of client affinity assignment with baseline.
* Fixed incorrect calculation
What about an idea to have a validation template file (e.g.
ignite-validate.xml), and make sure on startup that all config properties
specified in that file match. This way a user could put this file somewhere
on a shared network drive and have an extra degree of confidence that the
configuration i
Dear igniters,
please help do the code review for jira
https://issues.apache.org/jira/browse/IGNITE-8776
https://github.com/apache/ignite/pull/4300
Thanks,
kcheng.mvp
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Dmitry Konstantinov created IGNITE-8978:
---
Summary: Affinity throws "IgniteException: Failed to find cache"
after an Ignite client re-connect
Key: IGNITE-8978
URL: https://issues.apache.org/jira/browse/IGNITE
+1 (binding)
--
Denis
On Tue, Jul 10, 2018 at 10:02 AM Andrey Gura wrote:
> Igniters,
>
> We've uploaded a 2.6.0 release candidate to
> https://dist.apache.org/repos/dist/dev/ignite/2.6.0-rc1/
>
> Git tag name is 2.6.0-rc1.
>
> This release includes the following changes:
>
> Ignite:
> * Fixed
I see, then we need to come up with an external process-based solution for
the sake of the new ticket.
--
Denis
On Tue, Jul 10, 2018 at 6:01 AM Andrey Gura wrote:
> Denis,
>
> we have LongJVMPauseDetector. But it is Java thread that will be in
> safe-point during stop-the-world pause and theref
Not sure if this is worth a down vote, but the release notes seem like a
copy of 2.5 release. I think 2.6 should have its own release notes.
D.
On Tue, Jul 10, 2018 at 8:02 PM, Andrey Gura wrote:
> Igniters,
>
> We've uploaded a 2.6.0 release candidate to
> https://dist.apache.org/repos/dist/de
Anton,
Committing or rolling back from MXBean is OK, because it is not a listener,
but a direct invocation. However, it is not OK to allow synchronous
rollback from a filter or a listener. The only action you can do from a
listener is setRollbackOnly() which will cause the transaction to be rolled
Hi,
Please subscribe me.
--
Best regards,
Ivan Pavlukhin
Dmitry,
It is emergency release so we have very short list of changes. You could
check it using provided links.
ср, 11 июл. 2018 г., 3:01 Dmitriy Setrakyan :
> Not sure if this is worth a down vote, but the release notes seem like a
> copy of 2.5 release. I think 2.6 should have its own release
Sorry,
You could check it using provided links.
ср, 11 июл. 2018 г., 5:41 Andrey Gura :
> Dmitry,
>
> It is emergency release so we have very short list of changes. You could
> check it using provided links.
>
>
> ср, 11 июл. 2018 г., 3:01 Dmitriy Setrakyan :
>
>> Not sure if this is worth a d
Andrey, this is the link I have:
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.6.0-rc1
This list does not look short. It looks like a copy of 2.5.
D.
On Wed, Jul 11, 2018 at 5:48 AM, Andrey Gura wrote:
> Sorry,
>
> You could check it using
44 matches
Mail list logo
