Anton,
Thanks for effort on reducing PME blocking time.
I'm looking at.
чт, 5 дек. 2019 г. в 16:14, Anton Vinogradov :
> Igniters,
>
> Solution ready to be reviewed
> TeamCity is green:
>
>
Recording for those who couldn't join the webinar:
https://www.youtube.com/watch?v=fwMRFA7BWTk
Ivan, excellent presentation!
-
Denis
On Tue, Dec 3, 2019 at 4:41 PM Kseniya Romanova
wrote:
> Hi Humphrey! Checked in chrome and firefox - the link is alive and
> registration works. Please try
Thank you Alexey, yes I think all the webinar videos are recorded and
shared in youtube.
https://www.youtube.com/results?search_query=gridgain+webinar
I can share the webinar video once it is available.
On Sun, Dec 8, 2019 at 10:28 PM Alexey Zinoviev
wrote:
> Great to get a video after to
Hi Ivan, Ilya
Thank you for your reply. I have added you as dev in IgniteExtensions
project and you should be able to check the build configurations.
Yes, when I set artifact dependencies for ~Build Apache Ignite~ similar to
other projects then I receive below error
[ERROR] [ERROR] Could not
Ivan Rakov created IGNITE-12429:
---
Summary: Rework bytes-based WAL archive size management logic to
make historical rebalance more predictable
Key: IGNITE-12429
URL:
Hello!
I have found a regression to 2.7 which unfortunately was not caught by our
tests:
https://issues.apache.org/jira/browse/IGNITE-12428
It would be nice to fix it before releasing 2.8.
Regards,
--
Ilya Kasnacheev
пн, 9 дек. 2019 г. в 14:58, Ivan Pavlukhin :
> Maxim,
>
> > I see the
, 192.168.1.2],
sockAddrs=HashSet [/172.17.0.1:47500, /0:0:0:0:0:0:0:1%lo:47500,
/127.0.0.1:47500, /192.168.1.2:47500], discPort=47500, order=1, intOrder=1,
lastExchangeTime=1575909462941, loc=true, ver=2.7.0#20191209-sha1:,
isClient=false], topVer=1, nodeId8=895176bf, msg=null,
type
Pavel Tupitsyn created IGNITE-12427:
---
Summary: .NET: Ignite does not start under Mono on Linux because
of UnmanagedThread
Key: IGNITE-12427
URL: https://issues.apache.org/jira/browse/IGNITE-12427
Nikolay Izhikov created IGNITE-12426:
Summary: [IEP-35] Metric configuration: add node local
configuration
Key: IGNITE-12426
URL: https://issues.apache.org/jira/browse/IGNITE-12426
Project:
Thank you!
пн, 9 дек. 2019 г. в 19:08, Alexei Scherbakov :
>
> Ivan,
>
> It's true. The article is relevant for upcoming 2.8 release. I've added a
> remark on that.
>
> пн, 9 дек. 2019 г. в 15:44, Ivan Pavlukhin :
>
> > Alexei,
> >
> > Am I getting it right that the article is relevant for
Ivan,
It's true. The article is relevant for upcoming 2.8 release. I've added a
remark on that.
пн, 9 дек. 2019 г. в 15:44, Ivan Pavlukhin :
> Alexei,
>
> Am I getting it right that the article is relevant for current master
> and there is no released Ignite versions with described behavior? Is
That's ok, thanks.
> On 9 Dec 2019, at 17:49, Maxim Muzafarov wrote:
>
> Hello, Pert.
>
> The ignite-2.8 branch already exists on GitHub repository [1].
>
> I think this trigger can we removed since the TC.Bot has been
> configured [2] to run build nightly.
> Can you confirm that such
Hello, Pert.
The ignite-2.8 branch already exists on GitHub repository [1].
I think this trigger can we removed since the TC.Bot has been
configured [2] to run build nightly.
Can you confirm that such testing the release branch is OK ?
[1] https://github.com/apache/ignite/tree/ignite-2.8
[2]
Maxim, I saw you have deployed trigger for test on Ignite 2.8 branch via pull
request.
Are there problems with making real branch ignite-2.8 and putting it into
repository?
Thanks a lot!
On Mon, Dec 9, 2019 at 4:26 PM Ivan Pavlukhin wrote:
> Folks,
>
> All agents were cleaned.
>
> пн, 9 дек. 2019 г. в 09:13, Anton Vinogradov :
> >
> > aitc-lin03_01 also broken
> >
> > On Fri, Dec 6, 2019 at 2:49 PM Anton Vinogradov wrote:
> >
> > > listed agents seem to be broken
Folks,
All agents were cleaned.
пн, 9 дек. 2019 г. в 09:13, Anton Vinogradov :
>
> aitc-lin03_01 also broken
>
> On Fri, Dec 6, 2019 at 2:49 PM Anton Vinogradov wrote:
>
> > listed agents seem to be broken too:
> > aitc-lin11_02
> > aitc-lin10_02
> > aitc-lin05_01
> > aitc-lin04_04
> >
> > On
Alexei,
Am I getting it right that the article is relevant for current master
and there is no released Ignite versions with described behavior? Is
it mentioned in the document? Should we do it? What do you think?
вт, 3 дек. 2019 г. в 12:34, Alexei Scherbakov :
>
> Ivan,
>
> for me GG docs have
Ilya Kasnacheev created IGNITE-12425:
Summary: Deadlock on CacheStore.loadAll
Key: IGNITE-12425
URL: https://issues.apache.org/jira/browse/IGNITE-12425
Project: Ignite
Issue Type: Bug
Maxim,
> I see the issue [1] is unassigned. Do we have a person who will fix it
> bravely? :)
Let's wait Saikat as an original ticket contributor.
> P.S. The issue [1] doesn't seem to be a truly release `blocker`.
For me it sounds not good to intentionally include such behavior into
product
Mikhail,
I looked into PR [1] and left a couple of minor comments on GitHub.
But actually a real thing where I do not have enough expertise is a
notification firing strategy. From the first glance looks fine, but
there might be concerns I missed.
[1] https://github.com/apache/ignite/pull/7057
Hello!
I think that your build should depend on an Apache Ignite build(s) or just
use an already released version.
In the same fashion as all our teamcity depend on "Build Apache Ignite" and
use its artifacts.
Here you want Ignite snapshot but Teamcity does not know where to take it
from.
Ivan,
I see the issue [1] is unassigned. Do we have a person who will fix it
bravely? :)
If not I think it's better to revert the issue from the 2.8 release
branch and fix it in a calm manner in the master branch. I suppose
there will be enough of such changes to perform a next minor release
Igniters,
This month we united with Silicon Valley Java User Group and we'll be
repeating In-Memory Computing Essentials for Software Engineers session at
Google HQ.
Come over to meet in person, a lot of coding and practical examples. RSVP
using our local group below (and attend it to not miss
Saikat, igniters
I raised a blocker [1] for 2.8 related to recently implemented default
query timeout [2]. Currently we have a buggy behavior for thin JDBC
driver when a default timeout is configured.
Actually I see 2 options to go:
1. Fix the issue with thin JDBC [1].
2. Exclude a default query
Ivan Pavlukhin created IGNITE-12424:
---
Summary: Fix default query timeout behavior for thin JDBC
Key: IGNITE-12424
URL: https://issues.apache.org/jira/browse/IGNITE-12424
Project: Ignite
Saikat,
I cannot access a TC project using your link. It says:
"You do not have enough permissions to access project with internal
id: project28"
Could you please give an access or describe shortly how does a build
pipeline look like?
пн, 9 дек. 2019 г. в 06:40, Saikat Maitra :
>
> Hello,
>
> I
26 matches
Mail list logo
