Denis Magda created IGNITE-12101:
Summary: IgniteQueue.removeAll throws NPE
Key: IGNITE-12101
URL: https://issues.apache.org/jira/browse/IGNITE-12101
Project: Ignite
Issue Type: Bug
Build from sources, run yardstick test.
+1
>
>--- Forwarded message ---
>From: "Dmitriy Pavlov" < dpav...@apache.org >
>To: dev < dev@ignite.apache.org >
>Cc:
>Subject: [VOTE] Release Apache Ignite 2.7.6-rc1
>Date: Thu, 22 Aug 2019 20:11:58 +0300
>
>Dear Community,
>
>I have uploaded
Dmitriy,
Did you check RC using automated TeamCity task?
On Fri, Aug 23, 2019 at 11:09 AM Zhenya Stanilovsky
wrote:
> Build from sources, run yardstick test.
> +1
> >
> >--- Forwarded message ---
> >From: "Dmitriy Pavlov" < dpav...@apache.org >
> >To: dev < dev@ignite.apache.org >
>
In reply to
> Dmitriy,
> Did you check RC using automated TeamCity task?
Hi Anton,
Yes, it is now part of the process
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.4.VerifyReleasechangesusingTeamCity
Dmitriy,
This task checks nothing.
It just compares files with previous release.
On Fri, Aug 23, 2019 at 12:01 PM Dmitriy Pavlov wrote:
> In reply to
>
> > Dmitriy,
> > Did you check RC using automated TeamCity task?
>
> Hi Anton,
>
> Yes, it is now part of the process
>
>
>
Which TC task should release manager run?
I see screenshots made 2 releases ago and it shows `[2] Compare w/ Previous
Release`
Also, feel free to check the whole process of release to find out what else
can be obsolete
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
пт, 23
Dmitriy,
I'm talking about
https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum
It *MUST* be checked before Vote.
On Fri, Aug 23, 2019 at 1:17 PM Dmitriy Pavlov wrote:
> Which TC task should release manager run?
>
> I see
Do I understand correctly what only affected requests with "dirty" metadata
will be delayed, but not all ?
Doesn't this check hurt performance? Otherwise ALL requests will be blocked
until some unrelated metadata is written which is highly undesirable.
Otherwise looks good if performance will not
Alexei, If my understanding is correct (Denis please correct me if I'm
wrong) we'll indeed delay only reqs that touch "dirty" metadata (metadata
with unfinished write to disk).
I don't expect significant performance impact here because for now we don't
allow other threads to use "dirty" metadata
Dmitriy,
Since the same recommendations were provided at "[VOTE] Accept Apache
Ignite 2.7.5-rc3" and ... were ignored,
my -1 until this becomes a part of the release process.
On Fri, Aug 23, 2019 at 1:58 PM Anton Vinogradov wrote:
> Dmitriy,
>
> I'm talking about
>
Colin Cassidy created IGNITE-12096:
--
Summary: Ignite memory metrics incorrect on cache usage contraction
Key: IGNITE-12096
URL: https://issues.apache.org/jira/browse/IGNITE-12096
Project: Ignite
Antron,
it is outside of process until discussed. If I missed something where we
discussed and documented, please let me know.
Sorry, but one PMC member opinion about RC building process is not a part
of the RC building process. Feel free to discuss updates with the
community.
Despite is it not
My attempt was unsuccessful, please document or advice me how to use
https://ci.ignite.apache.org/viewLog.html?buildId=4530004=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum
пт, 23 авг. 2019 г. в 14:50, Dmitriy Pavlov :
> Antron,
>
> it is outside of process until discussed. If I
Hello, Dmitriy.
Seems, we have some issue here.
I also run this suite and got informative error [1]. You can find it in log:
```
[15:07:05] : [Step 6/8] [Maven Watcher]
[15:07:05]E: [Step 6/8] Failed to execute goal on project ignite-jta: Could
not resolve dependencies for project
-1 (binding)
Explained at discussion thread.
On Fri, Aug 23, 2019 at 11:17 AM Anton Vinogradov wrote:
> Dmitriy,
>
> Did you check RC using automated TeamCity task?
>
> On Fri, Aug 23, 2019 at 11:09 AM Zhenya Stanilovsky
> wrote:
>
>> Build from sources, run yardstick test.
>> +1
>> >
>>
Pavel Pereslegin created IGNITE-12097:
-
Summary: Code cleanup: useless GridDhtInvalidPartitionException
handling that cannot be thrown on demander (preloadEntry).
Key: IGNITE-12097
URL:
Maxim Muzafarov created IGNITE-12098:
Summary: Provide benchmark for the rebalance procedure
Key: IGNITE-12098
URL: https://issues.apache.org/jira/browse/IGNITE-12098
Project: Ignite
Denis Mekhanikov created IGNITE-12099:
-
Summary: Don't write metadata to disk in discovery thread
Key: IGNITE-12099
URL: https://issues.apache.org/jira/browse/IGNITE-12099
Project: Ignite
Sergey,
Yes, your understanding is similar to mine.
I created a JIRA ticket for this change:
https://issues.apache.org/jira/browse/IGNITE-12099
Denis
On 23 Aug 2019, 14:27 +0300, Sergey Chugunov , wrote:
> Alexei, If my understanding is correct (Denis please correct me if I'm
> wrong) we'll
I suppose the issue is in TC task or infra since I can clearly see
artifacts there
https://mvnrepository.com/artifact/org.jacorb/jacorb-idl/2.2.3-jonas-patch-20071018
also, it may be the same issue with
Maxim Muzafarov created IGNITE-12100:
Summary: Checkstyle must support TodoComment rule
Key: IGNITE-12100
URL: https://issues.apache.org/jira/browse/IGNITE-12100
Project: Ignite
Issue
Amit,
Yes, you should start with
https://ignite.apache.org/community/contribute.html#contribute. The Jira
board has the newbie filter:
https://issues.apache.org/jira/browse/IGNITE-12032?jql=project%20%3D%20IGNITE%20AND%20labels%20in%20(newbie)%20and%20status%20%3D%20OPEN
.
Feel free to solve
Hi Anton, Nikolay, Igniters,
I took 'Step 6' target ant parameters from the
https://ci.ignite.apache.org/buildConfiguration/ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum?
mvn clean install -Pall-java,all-scala,ml -DskipTests=true
and started it for the unpacked
I confirm that the release candidate can be successfully built locally, and
it is also clear from the build log that the TC task tries to access a
wrong repository.
Who has access to the TC and can clean the .m2 cache?
пт, 23 авг. 2019 г. в 16:27, Dmitriy Pavlov :
> I suppose the issue is in TC
Who has created the task in the first place and can check why it fails? I
see no reason to fail the release unless somebody can reasonably explain
what exactly wrong with the provided source package.
пт, 23 авг. 2019 г. в 17:51, Alexey Goncharuk :
> I confirm that the release candidate can be
+1
On Fri, Aug 23, 2019 at 3:32 PM Anton Vinogradov wrote:
>
> -1 (binding)
> Explained at discussion thread.
>
> On Fri, Aug 23, 2019 at 11:17 AM Anton Vinogradov wrote:
>
> > Dmitriy,
> >
> > Did you check RC using automated TeamCity task?
> >
> > On Fri, Aug 23, 2019 at 11:09 AM Zhenya
Thank you, Maksim. I will go through the design docs.
On Fri, Aug 23, 2019 at 7:16 AM Maksim Stepachev
wrote:
> Amit,
>
> Yes, you should start with
> https://ignite.apache.org/community/contribute.html#contribute. The Jira
> board has the newbie filter:
>
+1
Checked the source compilation and release package build, node start, and a
few examples. Left a comment on the failed TC task in the discussion thread.
пт, 23 авг. 2019 г. в 18:15, Andrey Gura :
> +1
>
> On Fri, Aug 23, 2019 at 3:32 PM Anton Vinogradov wrote:
> >
> > -1 (binding)
> >
Igor,
Make sense. I've fixed the implementation according to your proposal.
ср, 21 авг. 2019 г. в 17:59, Igor Sapego :
> Probably, we need separate configuration for
> Thin Clients as a part of ClientConnectorConfiguration?
>
> Best Regards,
> Igor
>
>
> On Thu, Aug 15, 2019 at 12:36 PM Alex
+1
пт, 23 авг. 2019 г. в 18:33, Alexey Goncharuk :
> +1
> Checked the source compilation and release package build, node start, and a
> few examples. Left a comment on the failed TC task in the discussion
> thread.
>
> пт, 23 авг. 2019 г. в 18:15, Andrey Gura :
>
> > +1
> >
> > On Fri, Aug 23,
+1, checked .NET node start and examples
On Fri, Aug 23, 2019 at 6:49 PM Alexei Scherbakov <
alexey.scherbak...@gmail.com> wrote:
> +1
>
> пт, 23 авг. 2019 г. в 18:33, Alexey Goncharuk >:
>
> > +1
> > Checked the source compilation and release package build, node start,
> and a
> > few
+1
Compiled from sources on Windows, started ignite.bat.
On Fri, Aug 23, 2019 at 10:52 PM Pavel Tupitsyn
wrote:
> +1, checked .NET node start and examples
>
> On Fri, Aug 23, 2019 at 6:49 PM Alexei Scherbakov <
> alexey.scherbak...@gmail.com> wrote:
>
> > +1
> >
> > пт, 23 авг. 2019 г. в 18:33,
+1
Checked: build from sources, startup node on Windows, simple topology,
version and copyright year output,
2.7.6-rc0 is used in the Apache Ignite Teamcity Bot since Sunday, Aug 18
2.7.6-rc1 (ver. 2.7.6#20190821-sha1:6b3acf40) installed as DB for the TC
Bot just now and the bot works well.
пт,
Denis,
Thin client uses BinaryHeapOutputStream, which uses Unsafe. I've got some
warnings when I run thin client with --illegal-access=debug flag, for
example:
WARNING: Illegal reflective access by
org.apache.ignite.internal.util.GridUnsafe$2
+1
Downloaded binaries, successfully assembled cluster.
Best Regards,
Ivan Rakov
On 23.08.2019 19:07, Dmitriy Pavlov wrote:
+1
Checked: build from sources, startup node on Windows, simple topology,
version and copyright year output,
2.7.6-rc0 is used in the Apache Ignite Teamcity Bot since
+1
Downloaded sources, successfully assembled and started.
--
Best regards,
Anton Kalashnikov
23.08.2019, 19:31, "Ivan Rakov" :
> +1
> Downloaded binaries, successfully assembled cluster.
>
> Best Regards,
> Ivan Rakov
>
> On 23.08.2019 19:07, Dmitriy Pavlov wrote:
>> +1
>>
>> Checked:
+1
have downloaded sources, built from the command line, run some
examples, checked SHA checksum
On Fri, 23 Aug 2019 at 19:38, Anton Kalashnikov wrote:
>
> +1
> Downloaded sources, successfully assembled and started.
>
>
> --
> Best regards,
> Anton Kalashnikov
>
>
> 23.08.2019, 19:31, "Ivan
+1
On Fri, Aug 23, 2019 at 9:40 AM Maxim Muzafarov wrote:
> +1
>
> have downloaded sources, built from the command line, run some
> examples, checked SHA checksum
>
> On Fri, 23 Aug 2019 at 19:38, Anton Kalashnikov wrote:
> >
> > +1
> > Downloaded sources, successfully assembled and started.
>
Hmm, looks like we need to provide some VM options for the thin clients as
well.
Alex, would you mind checking and sharing a full subset of such options for
the thin clients? I'll update the docs.
-
Denis
On Fri, Aug 23, 2019 at 9:23 AM Alex Plehanov
wrote:
> Denis,
>
> Thin client uses
Pavel,
ClientConnectorConfiguration is related to JDBC, ODBC and thin clients, the
new property only related to thin clients. If we put the new property
directly into ClientConnectorConfiguration, someone might think that it
also affects JDBC and ODBC.
пт, 23 авг. 2019 г. в 19:59, Pavel Tupitsyn
Denis,
Actually binary metadata is not stored in a metastore (however there
were a discussion about moving it). User scenario is valid. A
meaningful exception and documentation are good.
And also I can think about revisiting a needed configuration for
persistence in containerized environments.
+1
On Fri, Aug 23, 2019 at 11:42 PM Valentin Kulichenko
wrote:
>
> +1
>
> On Fri, Aug 23, 2019 at 9:40 AM Maxim Muzafarov wrote:
>
> > +1
> >
> > have downloaded sources, built from the command line, run some
> > examples, checked SHA checksum
> >
> > On Fri, 23 Aug 2019 at 19:38, Anton
42 matches
Mail list logo
