[jira] [Created] (IGNITE-14586) Remove @SupperessWarnings when implementation provided.

[Alexander Lapin (Jira)]

Alexander Lapin created IGNITE-14586:


 Summary: Remove @SupperessWarnings when implementation provided.
 Key: IGNITE-14586
 URL: https://issues.apache.org/jira/browse/IGNITE-14586
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexander Lapin






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Azure Cloud IP Finder

[Denis Magda]

Congrats, Atri!

Bragged about it a bit:
https://twitter.com/denismagda/status/1383104415087927297?s=20

--
Denis Magda,
VP, Developer Relations and Product Marketing




On Fri, Apr 16, 2021 at 12:57 PM Ilya Kasnacheev 
wrote:

> Hello!
>
> Thank you for driving this effort, Atri.
>
> The Azure IP Finder code has been merged and will surely be a highlight in
> Apache Ignite 2.11.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 14 апр. 2021 г. в 11:54, Atri Sharma :
>
> > Thanks for your comments.
> >
> > I have moved the dependency versions for shared versions to parent POM
> > and also for the majorly used versions for module specific
> > dependencies.
> >
> > I have also fixed the Ipv6 issue and have tested with both Ipv4 and
> > Ipv6 and it works fine.
> >
> > Please let me know your thoughts.
> >
> > Atri
> >
> > On Tue, Apr 13, 2021 at 9:39 PM Ilya Kasnacheev
> >  wrote:
> > >
> > > Hello!
> > >
> > > I have added more comments to the PR.
> > >
> > > IPv6 still needs to be supported and dependencies' versions should be
> > moved
> > > to parent/pom.xml, at least for shared dependencies such as log4j and
> > > jackson, and preferably for all dependencies.
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > вт, 13 апр. 2021 г. в 10:33, Atri Sharma :
> > >
> > > > Hello,
> > > >
> > > > Sorry for the late reply.
> > > >
> > > > Thank you for taking a look. Indeed, there were some issues and they
> > > > have now been fixed.
> > > >
> > > > I am able to start a two node cluster with Azure IPFinder enabled and
> > > > shut it down successfully (using Ipv4).
> > > >
> > > > Please see the latest iteration and let me know your thoughts and
> > comments.
> > > >
> > > > Regards,
> > > >
> > > > Atri
> > > >
> > > > On Fri, Apr 9, 2021 at 4:58 PM Ilya Kasnacheev
> > > >  wrote:
> > > > >
> > > > > Hello!
> > > > >
> > > > > I have responded to the ticket after testing on live Azure.
> > > > >
> > > > > Regards,
> > > > > --
> > > > > Ilya Kasnacheev
> > > > >
> > > > >
> > > > > пт, 9 апр. 2021 г. в 08:37, Atri Sharma :
> > > > >
> > > > > > Hi Ilya,
> > > > > >
> > > > > > Please let me know if I can help with any further iterations on
> > the PR.
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > Atri
> > > > > >
> > > > > > On Wed, Apr 7, 2021 at 5:04 PM Atri Sharma 
> > wrote:
> > > > > > >
> > > > > > > Hi Ilya,
> > > > > > >
> > > > > > > Thanks for taking a look. I was able to resolve dependencies
> > (Thanks,
> > > > > > > Sam!) and have updated the PR.
> > > > > > >
> > > > > > > Copying the jars from ignite-azure to libs works for me.
> > > > > > >
> > > > > > > Please see and let me know your thoughts.
> > > > > > >
> > > > > > > Regards,
> > > > > > >
> > > > > > > Atri
> > > > > > >
> > > > > > > On Mon, Apr 5, 2021 at 9:24 PM Ilya Kasnacheev
> > > > > > >  wrote:
> > > > > > > >
> > > > > > > > Hello again!
> > > > > > > >
> > > > > > > > I re-checked our cloud discovery options by moving
> ignite-aws,
> > > > > > ignite-gce,
> > > > > > > > ignite-cloud directories from lib/optional to lib/ and trying
> > to
> > > > run
> > > > > > Ignite
> > > > > > > > with simple config taken from examples.
> > > > > > > >
> > > > > > > > The results are the following:
> > > > > > > > ignite-aws seems to work (complains about unknown key)
> > > > > > > > ignite-gce seems to work too (complains about zero length
> key,
> > > > this is
> > > > > > > > before it tries any network access so maybe there are other
> > issues
> > > > > > down the
> > > > > > > > path)
> > > > > > > > ignite-cloud (jclouds) DOES NOT work. Filed
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-14481 . I guess
> > this
> > > > > > discovery
> > > > > > > > finder is not widely used.
> > > > > > > > ignite-azure, presently, will not work too. Please use
> > ignite-aws
> > > > as an
> > > > > > > > example since it sees the most usage.
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > --
> > > > > > > > Ilya Kasnacheev
> > > > > > > >
> > > > > > > >
> > > > > > > > пн, 5 апр. 2021 г. в 16:05, Ilya Kasnacheev <
> > > > ilya.kasnach...@gmail.com
> > > > > > >:
> > > > > > > >
> > > > > > > > > Hello!
> > > > > > > > >
> > > > > > > > > I'm not sure that I can see any attachment to your e-mail.
> > Can
> > > > you
> > > > > > please
> > > > > > > > > re-send?
> > > > > > > > >
> > > > > > > > > We could have broken some of those, I guess, since we seem
> to
> > > > not run
> > > > > > > > > integration tests for them.
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > --
> > > > > > > > > Ilya Kasnacheev
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > пт, 2 апр. 2021 г. в 12:59, Atri Sharma :
> > > > > > > > >
> > > > > > > > >> Hello,
> > > > > > > > >>
> > > > > > > > >> Thank you for sharing.
> > > > > > > > >>
> > > > > > > > >> I was finally able to replicate the issue. However, I
> tried
> > with
> > > > > > other
> > > > > > > > >> IPFinders and 

Re: Welcome letter

[Eduard Rakhmankulov]

Thank you so much!

On Fri, 16 Apr 2021, 18:15 Denis Magda,  wrote:

> Hi Eduard,
>
> Welcome to the community! I see that someone has already added you to the
> contributors' list in JIRA. Good luck, pick your ticket!
>
> -
> Denis
>
>
> On Thu, Apr 15, 2021 at 8:52 AM Eduard Rakhmankulov 
> wrote:
>
> > Hello Ignite Community!
> >
> > My name is Eduard. I want to contribute to Apache Ignite, my JIRA
> username
> > *erixon*.
> >
> > Thanks!
> >
> > --
> > Best regards, Eduard.
> >
>

Re: Azure Cloud IP Finder

[Ilya Kasnacheev]

Hello!

Thank you for driving this effort, Atri.

The Azure IP Finder code has been merged and will surely be a highlight in
Apache Ignite 2.11.

Regards,
-- 
Ilya Kasnacheev


ср, 14 апр. 2021 г. в 11:54, Atri Sharma :

> Thanks for your comments.
>
> I have moved the dependency versions for shared versions to parent POM
> and also for the majorly used versions for module specific
> dependencies.
>
> I have also fixed the Ipv6 issue and have tested with both Ipv4 and
> Ipv6 and it works fine.
>
> Please let me know your thoughts.
>
> Atri
>
> On Tue, Apr 13, 2021 at 9:39 PM Ilya Kasnacheev
>  wrote:
> >
> > Hello!
> >
> > I have added more comments to the PR.
> >
> > IPv6 still needs to be supported and dependencies' versions should be
> moved
> > to parent/pom.xml, at least for shared dependencies such as log4j and
> > jackson, and preferably for all dependencies.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > вт, 13 апр. 2021 г. в 10:33, Atri Sharma :
> >
> > > Hello,
> > >
> > > Sorry for the late reply.
> > >
> > > Thank you for taking a look. Indeed, there were some issues and they
> > > have now been fixed.
> > >
> > > I am able to start a two node cluster with Azure IPFinder enabled and
> > > shut it down successfully (using Ipv4).
> > >
> > > Please see the latest iteration and let me know your thoughts and
> comments.
> > >
> > > Regards,
> > >
> > > Atri
> > >
> > > On Fri, Apr 9, 2021 at 4:58 PM Ilya Kasnacheev
> > >  wrote:
> > > >
> > > > Hello!
> > > >
> > > > I have responded to the ticket after testing on live Azure.
> > > >
> > > > Regards,
> > > > --
> > > > Ilya Kasnacheev
> > > >
> > > >
> > > > пт, 9 апр. 2021 г. в 08:37, Atri Sharma :
> > > >
> > > > > Hi Ilya,
> > > > >
> > > > > Please let me know if I can help with any further iterations on
> the PR.
> > > > >
> > > > > Regards,
> > > > >
> > > > > Atri
> > > > >
> > > > > On Wed, Apr 7, 2021 at 5:04 PM Atri Sharma 
> wrote:
> > > > > >
> > > > > > Hi Ilya,
> > > > > >
> > > > > > Thanks for taking a look. I was able to resolve dependencies
> (Thanks,
> > > > > > Sam!) and have updated the PR.
> > > > > >
> > > > > > Copying the jars from ignite-azure to libs works for me.
> > > > > >
> > > > > > Please see and let me know your thoughts.
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > Atri
> > > > > >
> > > > > > On Mon, Apr 5, 2021 at 9:24 PM Ilya Kasnacheev
> > > > > >  wrote:
> > > > > > >
> > > > > > > Hello again!
> > > > > > >
> > > > > > > I re-checked our cloud discovery options by moving ignite-aws,
> > > > > ignite-gce,
> > > > > > > ignite-cloud directories from lib/optional to lib/ and trying
> to
> > > run
> > > > > Ignite
> > > > > > > with simple config taken from examples.
> > > > > > >
> > > > > > > The results are the following:
> > > > > > > ignite-aws seems to work (complains about unknown key)
> > > > > > > ignite-gce seems to work too (complains about zero length key,
> > > this is
> > > > > > > before it tries any network access so maybe there are other
> issues
> > > > > down the
> > > > > > > path)
> > > > > > > ignite-cloud (jclouds) DOES NOT work. Filed
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-14481 . I guess
> this
> > > > > discovery
> > > > > > > finder is not widely used.
> > > > > > > ignite-azure, presently, will not work too. Please use
> ignite-aws
> > > as an
> > > > > > > example since it sees the most usage.
> > > > > > >
> > > > > > > Regards,
> > > > > > > --
> > > > > > > Ilya Kasnacheev
> > > > > > >
> > > > > > >
> > > > > > > пн, 5 апр. 2021 г. в 16:05, Ilya Kasnacheev <
> > > ilya.kasnach...@gmail.com
> > > > > >:
> > > > > > >
> > > > > > > > Hello!
> > > > > > > >
> > > > > > > > I'm not sure that I can see any attachment to your e-mail.
> Can
> > > you
> > > > > please
> > > > > > > > re-send?
> > > > > > > >
> > > > > > > > We could have broken some of those, I guess, since we seem to
> > > not run
> > > > > > > > integration tests for them.
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > --
> > > > > > > > Ilya Kasnacheev
> > > > > > > >
> > > > > > > >
> > > > > > > > пт, 2 апр. 2021 г. в 12:59, Atri Sharma :
> > > > > > > >
> > > > > > > >> Hello,
> > > > > > > >>
> > > > > > > >> Thank you for sharing.
> > > > > > > >>
> > > > > > > >> I was finally able to replicate the issue. However, I tried
> with
> > > > > other
> > > > > > > >> IPFinders and ran into the same problem (attached are the
> logs).
> > > > > > > >>
> > > > > > > >> Not sure what is causing this?
> > > > > > > >>
> > > > > > > >> Atri
> > > > > > > >>
> > > > > > > >> On Fri, Apr 2, 2021 at 2:29 PM Ilya Kasnacheev
> > > > > > > >>  wrote:
> > > > > > > >> >
> > > > > > > >> > Hello!
> > > > > > > >> >
> > > > > > > >> > Please find attached the log file of errors. This is
> > > yesterday's
> > > > > (Apr
> > > > > > > >> 1) build.
> > > > > > > >> >
> > > > > > > >> > Regards,
> > > > > > > >> > --
> > > > > > > >> > Ilya Kasnacheev
> > > > > > > >> >
> > > > > > > 

[jira] [Created] (IGNITE-14585) Ability to extend config files in spec

[Nikolay Izhikov (Jira)]

Nikolay Izhikov created IGNITE-14585:


 Summary: Ability to extend config files in spec
 Key: IGNITE-14585
 URL: https://issues.apache.org/jira/browse/IGNITE-14585
 Project: Ignite
  Issue Type: Improvement
Reporter: Nikolay Izhikov
Assignee: Nikolay Izhikov


Right now extensions of {{IgniteSpec}} can't provide custom config files and 
it's templates because only template returned from spec if 
{{IgniteConfigTemplate}}.

We need to return array of tuples from {{IgniteSpec#config_templates}} that 
specify config files required to be generated to run Ignite based node.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14584) Server node fails on remote filter with static initializer deployment if client disconnects

[Igor Belyakov (Jira)]

Igor Belyakov created IGNITE-14584:
--

 Summary: Server node fails on remote filter with static 
initializer deployment if client disconnects
 Key: IGNITE-14584
 URL: https://issues.apache.org/jira/browse/IGNITE-14584
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.10
Reporter: Igor Belyakov
Assignee: Igor Belyakov


Cluster contains 1 server and 1 client node. PeerClassLoading is turned on.
1. Client node deploys CQ with remote filter, server node doesn't have classes 
required for remote filter in classpath. Remote filter should has a class with 
static initializer, which has a type that should be deployed:

 
{code:java}
public class TestClass {
 static {
 TestSubClass testSubClass = new TestSubClass();
 }
}
public class TestSubClass {
}
{code}
 

2. When TestSubClass deployment is in progress on the server node, the client 
node is stopped
3. The server node is unable to deploy TestSubClass and static initializer 
can't be finished, as result java.lang.ExceptionInInitializerError happens in 
discovery thread and server node fails:
{code:java}
[16:56:23,829][WARNING][disco-notifier-worker-#49%srv1%][GridDeploymentPerVersionStore]
 Failed to send class-loading request to node (is node alive?) 
[node=72513f9a-8053-410c-bc4f-aa4935e06661, clsName=TestSubClass, 
clsPath=TestSubClass.class, 
clsLdrId=1ca6c09f471-72513f9a-8053-410c-bc4f-aa4935e06661, 
parentClsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2][16:56:23,829][WARNING][disco-notifier-worker-#49%srv1%][GridDeploymentPerVersionStore]
 Failed to send class-loading request to node (is node alive?) 
[node=72513f9a-8053-410c-bc4f-aa4935e06661, clsName=TestSubClass, 
clsPath=TestSubClass.class, 
clsLdrId=1ca6c09f471-72513f9a-8053-410c-bc4f-aa4935e06661, 
parentClsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2][16:56:23,829][SEVERE][disco-notifier-worker-#49%srv1%][GridDiscoveryManager]
 Exception in discovery notifier worker 
thread.java.lang.ExceptionInInitializerError at java.lang.Class.forName0(Native 
Method) at java.lang.Class.forName(Class.java:348) at 
org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:9066) at 
org.apache.ignite.internal.MarshallerContextImpl.getClass(MarshallerContextImpl.java:325)
 at 
org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:640)
 at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1755)
 at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1714)
 at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1976)
 at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read0(BinaryFieldAccessor.java:702)
 at 
org.apache.ignite.internal.binary.BinaryFieldAccessor.read(BinaryFieldAccessor.java:187)
 at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:887)
 at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize0(BinaryReaderExImpl.java:1762)
 at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1714)
 at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:315)
 at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:300)
 at 
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:100)
 at 
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:80)
 at 
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10573) 
at 
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10602) 
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryDeployableObject.unmarshal(CacheContinuousQueryDeployableObject.java:96)
 at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.p2pUnmarshal(CacheContinuousQueryHandler.java:1308)
 at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.p2pUnmarshal(CacheContinuousQueryHandler.java:1283)
 at 
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.processStartRequest(GridContinuousProcessor.java:1408)
 at 
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.access$400(GridContinuousProcessor.java:113)
 at 
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:205)
 at 
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$2.onCustomEvent(GridContinuousProcessor.java:196)
 at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:655)
 at 

[jira] [Created] (IGNITE-14583) Server node fails on remote filter deployment after client reconnect with new node id

[Igor Belyakov (Jira)]

Igor Belyakov created IGNITE-14583:
--

 Summary: Server node fails on remote filter deployment after 
client reconnect with new node id
 Key: IGNITE-14583
 URL: https://issues.apache.org/jira/browse/IGNITE-14583
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.10
Reporter: Igor Belyakov
Assignee: Igor Belyakov


Cluster contains 1 server and 1 client node. PeerClassLoading turned on.

*1.* Client node deploys CQ with remote filter, server node doesn't have 
classes required for remote filter in classpath.

*2.* Remote filter successfully deployed to server node.

*3.* Client node disconnects and reconnects by using new node id:

[15:44:43] Client node was reconnected after it was already considered failed 
by the server topology (this could happen after all servers restarted or due to 
a long network outage between the client and servers). All continuous queries 
and remote event listeners created by this client will be unsubscribed, 
consider listening to EVT_CLIENT_NODE_RECONNECTED event to restore them.

*4.* On connect, client node tries to deploy remote filter to server node, but 
server node fails due to wrong ClassLoaderId, which is sent in 
GridDeploymentInfo (used ClassLoaderId for old client node):

[15:44:42] (err) Failed to notify listener: 
o.a.i.i.util.future.GridFutureChainListener@778d0fc6class 
org.apache.ignite.IgniteException: Failed to initialize a remote filter.
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.lambda$register$2bf956f5$1(CacheContinuousQueryHandler.java:353)
at 
org.apache.ignite.internal.util.future.GridFutureChainListener.applyCallback(GridFutureChainListener.java:77)
at 
org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:69)
at 
org.apache.ignite.internal.util.future.GridFutureChainListener.apply(GridFutureChainListener.java:29)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:398)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:346)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:334)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:510)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:489)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:477)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.p2pUnmarshal(CacheContinuousQueryHandler.java:1311)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.p2pUnmarshal(CacheContinuousQueryHandler.java:1283)
at 
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$8.run(GridContinuousProcessor.java:693)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7162)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:826)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: class org.apache.ignite.internal.IgniteDeploymentCheckedException: 
Failed to obtain deployment for class: Client1$$Lambda$513/0x0008003b8840
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryDeployableObject.unmarshal(CacheContinuousQueryDeployableObject.java:94)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.p2pUnmarshal(CacheContinuousQueryHandler.java:1308)
... 8 more
авг. 07, 2020 3:44:42 PM org.apache.ignite.logger.java.JavaLogger error
SEVERE: Failed to unmarshal continuous routine handler 
[routineId=8f0137dc-cb32-40ff-83f4-867f272d338e, 
srcNodeId=ebcf4d5b-a476-43d5-b057-00b5694104e6]
class org.apache.ignite.internal.IgniteDeploymentCheckedException: Failed to 
obtain deployment for class: Client1$$Lambda$513/0x0008003b8840
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryDeployableObject.unmarshal(CacheContinuousQueryDeployableObject.java:94)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.p2pUnmarshal(CacheContinuousQueryHandler.java:1308)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.p2pUnmarshal(CacheContinuousQueryHandler.java:1283)
at 
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor$8.run(GridContinuousProcessor.java:693)
at 

[jira] [Created] (IGNITE-14582) Continuous Query deploys remote filter even on client nodes

[Igor Belyakov (Jira)]

Igor Belyakov created IGNITE-14582:
--

 Summary: Continuous Query deploys remote filter even on client 
nodes
 Key: IGNITE-14582
 URL: https://issues.apache.org/jira/browse/IGNITE-14582
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.10
Reporter: Igor Belyakov
Assignee: Igor Belyakov
 Attachments: CacheContinuousQueryDeploymentToClientTest.java

When the client node joins cluster CQ routine is deployed on it, but there's no 
sense to have CQ on the client node which doesn't store any data at all.

Test attached.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14581) Implement IgniteImpl close method

[Alexander Lapin (Jira)]

Alexander Lapin created IGNITE-14581:


 Summary: Implement IgniteImpl close method
 Key: IGNITE-14581
 URL: https://issues.apache.org/jira/browse/IGNITE-14581
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexander Lapin
Assignee: Alexander Lapin






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14580) Add exception handling logic to IgntitionProcessor

[Alexander Lapin (Jira)]

Alexander Lapin created IGNITE-14580:


 Summary: Add exception handling logic to IgntitionProcessor
 Key: IGNITE-14580
 URL: https://issues.apache.org/jira/browse/IGNITE-14580
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexander Lapin
Assignee: Alexander Lapin


Handle Ignition service lack and throw proper exception from start method.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14579) Start rest manager

[Alexander Lapin (Jira)]

Alexander Lapin created IGNITE-14579:


 Summary: Start rest manager
 Key: IGNITE-14579
 URL: https://issues.apache.org/jira/browse/IGNITE-14579
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexander Lapin
Assignee: Alexander Lapin


Update IgntionImpl with code that will start rest manager.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14578) Bootstrap configuation manager with distributed configuraiton

[Alexander Lapin (Jira)]

Alexander Lapin created IGNITE-14578:


 Summary: Bootstrap configuation manager with distributed 
configuraiton
 Key: IGNITE-14578
 URL: https://issues.apache.org/jira/browse/IGNITE-14578
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexander Lapin
Assignee: Alexander Lapin


Update IgntionImpl with code that will 
* Add distributed root keys.
* Bootstrap distributed configuration.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14577) .NET: error serialization failed when thread is interrupted

[Pavel Tupitsyn (Jira)]

Pavel Tupitsyn created IGNITE-14577:
---

 Summary: .NET: error serialization failed when thread is 
interrupted
 Key: IGNITE-14577
 URL: https://issues.apache.org/jira/browse/IGNITE-14577
 Project: Ignite
  Issue Type: New Feature
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn


When using {{ICompute.WithTimeout}}, the following scenario is possible:
* Timeout is reached, and Ignite interrupts compute job thread
* {{InterruptedException}} is thrown from the job code
* Ignite.NET tries to serialize the job result (exception) in 
{{BinaryUtils.WriteInvocationResult}}
* {{BinaryProcessor.PutBinaryTypes}} is called during the serialization
* Thread is interrupted, so metadata update fails with {{InterruptedException}}

As a result, instead of a simple timeout exception, there is a lot of cryptic 
errors in the log.

Possible fixes:
* Handle {{InterruptedException}} as a special case in {{WriteInvocationResult}}
* Do not interrupt binary meta updates



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Welcome letter

[Denis Magda]

Hi Eduard,

Welcome to the community! I see that someone has already added you to the
contributors' list in JIRA. Good luck, pick your ticket!

-
Denis


On Thu, Apr 15, 2021 at 8:52 AM Eduard Rakhmankulov 
wrote:

> Hello Ignite Community!
>
> My name is Eduard. I want to contribute to Apache Ignite, my JIRA username
> *erixon*.
>
> Thanks!
>
> --
> Best regards, Eduard.
>

Re: [VOTE] Release pyignite 0.4.0-rc1

[Igor Sapego]

+1 from me.

Best Regards,
Igor


On Fri, Apr 16, 2021 at 5:05 PM Ivan Daschinsky 
wrote:

> Ivan Daschinsky 
> чт, 15 апр., 21:37 (19 часов назад)
> кому: dev
> Dear Igniters!
>
> Release candidate binaries are at least uploaded and ready for vote
> You can find them here:
> https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.4.0-rc1
>
> If you follow the link above, you will find source package (*.tar.gz and
> *.zip)
> and binary packages (wheels) for windows (x86, amd64) and linux (x86 and
> x86_64)
> for pythons 36, 37, 38, 39. Also, there are sha512 and gpg signatures.
>
> You can install binary package for specific version of python using pip
> For example do this on linux for python 3.8
> >> pip install pyignite-0.4.0-cp38-cp38-manylinux1_x86_64.whl
>
> You can build and install package from source using this command:
> >> pip install pyignite-0.4.0.tar.gz
> You can build wheel on your platform using this command:
> >> pip wheel --no-deps pyignite-0.4.0.tar.gz
>
> For building C module, you should have python headers and C compiler
> installed.
> (i.e. for ubuntu sudo apt install build-essential python3-dev)
> In Mac OS X xcode-tools and python from homebrew are the best option.
>
> In order to check whether C module works, use following:
> >> from pyignite import _cutils
> >> print(_cutils.hashcode('test'))
> >> 3556498
>
> You can find documentation here:
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.4.0.rc1
>
> You can find examples here (to check them, you should start ignite
> locally):
>
> https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.4.0.rc1/examples.html
> Also, examples can be found in source archive in examples subfolder.
> docker-compose.yml is supplied in order to start ignite quickly.
>
> Release notes:
>
> https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=blob;f=RELEASE_NOTES.txt;h=9fee8ead3f70718767f6e11f93d1c7e77c61657b;hb=466b54527e6e42bc585c594d840a959d0b8626ef
>
> Git release tag was created:
>
> https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=tag;h=refs/tags/0.4.0.rc1
>
> The vote is formal, see voting guidelines
> https://www.apache.org/foundation/voting.html
>
> +1 - to accept pyignite-0.4.0-rc1
> 0 - don't care either way
> -1 - DO NOT accept pyignite-0.4.0-rc1
>
> The vote will end at April, 21 15:00 UTC.
>

[jira] [Created] (IGNITE-14576) Ignite command-line tool cannot stop already running ignite instance

[Vyacheslav Koptilin (Jira)]

Vyacheslav Koptilin created IGNITE-14576:


 Summary: Ignite command-line tool cannot stop already running 
ignite instance
 Key: IGNITE-14576
 URL: https://issues.apache.org/jira/browse/IGNITE-14576
 Project: Ignite
  Issue Type: Bug
 Environment: 

Reporter: Vyacheslav Koptilin


Ignite command-line tool cannot stop already running ignite instance.

Steps to reproduce:
1. start Ignite node 
{code:bash}
PS C:\projects\ignite-3\modules\cli\target> ./ignite node start 
consistent-id=
Starting a new Ignite node...

Node is successfully started. To stop, type ignite node stop consistent-id=

+---+---+
| Consistent ID | consistent-id=
|
+---+---+
| PID   | 17476 
|
+---+---+
| Log File  | 
C:\projects\ignite-3\modules\cli\target\ignite-log\consistent-id=.log |
+---+---+
{code}

2. make sure that Ignite node has been started

{code:bash}
PS C:\projects\ignite-3\modules\cli\target> ./ignite node list
Currently, there are 1 locally running nodes.

++---+---+
| Consistent ID  | PID   | Log File 
 |
++---+---+
| consistent-id= | 17476 | 
C:\projects\ignite-3\modules\cli\target\ignite-log\consistent-id=.log |
++---+---+
{code}

3 try to stop the node

{code:bash}
PS C:\projects\ignite-3\modules\cli\target> ./ignite node stop 
consistent-ids=
Can't find node with consistent id consistent-ids=
{code}

The root cause is obvious. The tool tries to find 
{{consistentId*s*=_...pid}} file instead of {{consistent-id=_...pid}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[VOTE] Release pyignite 0.4.0-rc1

[Ivan Daschinsky]

Ivan Daschinsky 
чт, 15 апр., 21:37 (19 часов назад)
кому: dev
Dear Igniters!

Release candidate binaries are at least uploaded and ready for vote
You can find them here:
https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.4.0-rc1

If you follow the link above, you will find source package (*.tar.gz and
*.zip)
and binary packages (wheels) for windows (x86, amd64) and linux (x86 and
x86_64)
for pythons 36, 37, 38, 39. Also, there are sha512 and gpg signatures.

You can install binary package for specific version of python using pip
For example do this on linux for python 3.8
>> pip install pyignite-0.4.0-cp38-cp38-manylinux1_x86_64.whl

You can build and install package from source using this command:
>> pip install pyignite-0.4.0.tar.gz
You can build wheel on your platform using this command:
>> pip wheel --no-deps pyignite-0.4.0.tar.gz

For building C module, you should have python headers and C compiler
installed.
(i.e. for ubuntu sudo apt install build-essential python3-dev)
In Mac OS X xcode-tools and python from homebrew are the best option.

In order to check whether C module works, use following:
>> from pyignite import _cutils
>> print(_cutils.hashcode('test'))
>> 3556498

You can find documentation here:
https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.4.0.rc1

You can find examples here (to check them, you should start ignite locally):
https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.4.0.rc1/examples.html
Also, examples can be found in source archive in examples subfolder.
docker-compose.yml is supplied in order to start ignite quickly.

Release notes:
https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=blob;f=RELEASE_NOTES.txt;h=9fee8ead3f70718767f6e11f93d1c7e77c61657b;hb=466b54527e6e42bc585c594d840a959d0b8626ef

Git release tag was created:
https://gitbox.apache.org/repos/asf?p=ignite-python-thin-client.git;a=tag;h=refs/tags/0.4.0.rc1

The vote is formal, see voting guidelines
https://www.apache.org/foundation/voting.html

+1 - to accept pyignite-0.4.0-rc1
0 - don't care either way
-1 - DO NOT accept pyignite-0.4.0-rc1

The vote will end at April, 21 15:00 UTC.

Re: [DISCUSSION] Error handling in Ignite 3

[Alexei Scherbakov]

чт, 15 апр. 2021 г. в 18:21, Andrey Mashenkov :

> Hi Alexey,
> I like the idea.
>
> 1.
>
> >   TBL-0001 is a *string representation* of the error. It is built from 2
> > byte scope id (mapped to name TBL) and 2 byte number (0001). Both
> > internally packed in int. No any kind of parsing will be necessary to
> read
> > scope/category.
>
> I think Alexey mean if it will be possible to make smth like that
>
> catch (IgniteException e) {
> if (e.getScope() == "TBL" && e.getCode() == 1234)
> continue; // E.g. retry my TX
> }
>
> It looks useful to me.
>

I have in mind something like this:

public class IgniteException extends RuntimeException {
private int errorCode;

public IgniteException(ErrorScope scope, int code, String message,
Throwable cause) {
super(message, cause);
this.errorCode = make(scope, code);
}

public boolean matches(ErrorScope scope, int code) {
return errorCode == make(scope, code);
}

private int make(ErrorScope scope, int code) {
return ((scope.ordinal() << 16) | code);
}

public ErrorScope scope() {
return ErrorScope.values()[errorCode >> 16];
}

public int code() {
return 0x & errorCode;
}

public static void main(String[] args) {
IgniteException e = new IgniteException(ErrorScope.RAFT, 1, "test",
null);

System.out.println(e.matches(ErrorScope.RAFT, 2));
System.out.println(e.scope());
System.out.println(e.code());

try {
throw e;
}
catch (IgniteException ee) {
System.out.println(ee.matches(ErrorScope.RAFT, 1));
}
}
}


>
> 2. How you see a cross-module exception throwing?
> Assume, user call -> module A, which recursively call -> module B, which
> fails.
> So, module A component calls a module B component and got an Exception with
> "B-1234" exception.
> Module A do not expect any exception here and doesn't take care of "B-xxx"
> error codes, but only "A-.
> Should it rethrow exception with "A-unknown" (maybe "UNK-0001") code
> or reuse "B-" code with the own message, pointing original exception as
> a cause for both cases?
>
> The first approach may looks confusing, while the second one produces too
> many "UNK-" codes.
> What code should get the user in that case?
>
>
>
The method should always report root cause, in your example it will be
B-, no matter which module API is called.


>
>
>
> On Thu, Apr 15, 2021 at 5:36 PM Alexei Scherbakov <
> alexey.scherbak...@gmail.com> wrote:
>
> > чт, 15 апр. 2021 г. в 14:26, Ilya Kasnacheev  >:
> >
> > > Hello!
> > >
> > > > All public methods throw only unchecked
> > > org.apache.ignite.lang.IgniteException containing aforementioned
> fields.
> > > > Each public method must have a section in the javadoc with a list of
> > all
> > > possible error codes for this method.
> > >
> > > I don't think this is feasible at all.
> > > Imagine javadoc for cache.get() method featuring three pages of
> possible
> > > error codes thrown by this method.
> > >
> >
> > Of course there is no need to write 3 pages of error codes, this makes no
> > sense.
> > I think we can use error ranges here, or, probably, document most
> important
> > error scenarios.
> > The point here is to try to document errors as much as possible.
> >
> >
> > > Also, updated every two weeks to account for changes in
> > > underlying mechanisms.
> > >
> > > There is still a confusion between "error code for any error in logs"
> and
> > > "error code for any pair of method & exception". Which one are we
> > > discussing really?
> > >
> > > This is impossible to track or test, but is susceptible for common
> > > error-hiding antipattern where all exceptions are caught in cache.get()
> > and
> > > discarded, and instead a brand new CH-0001 "error in cache.get()" is
> > thrown
> > > to the user.
> > >
> > > Which is certainly not something that anybody wants.
> > >
> >
> > Certainly not. We are talking here about root cause - what is exactly the
> > reason for method call failure.
> >
> >
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > чт, 15 апр. 2021 г. в 13:03, Vladislav Pyatkov :
> > >
> > > > Hi Alexei,
> > > >
> > > > > Each public method *must *have a section in the javadoc with a list
> > of
> > > > all possible error codes for this method.
> > > >
> > > > I consider it is redundant, because any public exception can be
> thrown
> > > from
> > > > public API.
> > > > If it not happens today, it may change tomorrow: one will be removed,
> > > > another one will be added.
> > > >
> > > > >Nested exceptions are not forbidden to use. They can provide
> > additional
> > > > details on the error for debug purposes
> > > >
> > > > I see another issue, which is in the Ignite 2.x, but not attend here.
> > We
> > > > can have a deep nested exception and use it for handling.
> > > > In the result, all time when we are handling an exception we use
> > > > 

[jira] [Created] (IGNITE-14575) Write to Distributed Metastorage should throw exception on client if client is not connected to topology

[Semyon Danilov (Jira)]

Semyon Danilov created IGNITE-14575:
---

 Summary: Write to Distributed Metastorage should throw exception 
on client if client is not connected to topology
 Key: IGNITE-14575
 URL: https://issues.apache.org/jira/browse/IGNITE-14575
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.10
Reporter: Semyon Danilov
Assignee: Semyon Danilov


Reference to Distributed Metastorage can be obtained on client that hasn't 
connected to any server node yet.

The reference allows to send write request that will be completed after client 
connect when Tcp Discovery is used and dropped on ZK Discovery.

To make API more reliable we need to change this behavior: when client is not 
connected to any server (because there are no servers in topology yet or 
because it has disconnected from topology) all incoming write or cas requests 
should be dropped, appropriate exception should be thrown.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14574) Ignite command-line tool cannot download a maven artifact from local repository on Windows platform

[Vyacheslav Koptilin (Jira)]

Vyacheslav Koptilin created IGNITE-14574:


 Summary: Ignite command-line tool cannot download a maven artifact 
from local repository on Windows platform
 Key: IGNITE-14574
 URL: https://issues.apache.org/jira/browse/IGNITE-14574
 Project: Ignite
  Issue Type: Bug
Reporter: Vyacheslav Koptilin


Ignite command-line tool cannot download a maven artifact from local repository 
on Windows platform

{code:java}
PS C:\projects\ignite-3\modules\cli\target> ./ignite.exe init
Creating directories... Done!
++---+
| Binaries Directory | C:\projects\ignite-3\modules\cli\target\ignite-bin|
++---+
| Work Directory | C:\projects\ignite-3\modules\cli\target\ignite-work   |
++---+
| Config Directory   | C:\projects\ignite-3\modules\cli\target\ignite-config |
++---+
| Log Directory  | C:\projects\ignite-3\modules\cli\target\ignite-log|
++---+

file://C:\Users\user\.m2\repository
Installing org.apache.ignite:ignite-runner:3.0.0-SNAPSHOT...
|>  
   |  1%
[unresolved dependency: org.apache.ignite#ignite-runner;3.0.0-SNAPSHOT: not 
found]
{code}

It seems, that the root cause of the issue is the file URI schema:

{code:java|title:MavenArtifactResolver.java}
private Ivy ivyInstance(List repositories) {
...
locBr.setRoot("file://" + 
pathRslvr.osHomeDirectoryPath().resolve(".m2").resolve("repository/"));
}
...
{code}

Perhaps, the proper fix is to change "file://" to "file:///"



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14573) Calcite bug. DML operations skips binary flag usage.

[Stanilovsky Evgeny (Jira)]

Stanilovsky Evgeny created IGNITE-14573:
---

 Summary: Calcite bug. DML operations skips binary flag usage.
 Key: IGNITE-14573
 URL: https://issues.apache.org/jira/browse/IGNITE-14573
 Project: Ignite
  Issue Type: Improvement
  Components: sql
Reporter: Stanilovsky Evgeny
Assignee: Stanilovsky Evgeny


As a result, insert with further read operations will fail.
For example:

{code:java}
CREATE TABLE IF NOT EXISTS test (id INTEGER, a INTEGER);
INSERT INTO test VALUES (1, 1), (2, 2), (3, 3), (4, NULL);"
UPDATE test SET a=CASE WHEN id=1 THEN 7 ELSE NULL END WHERE id <= 2";
{code}




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14572) Include metastorage into snapshot

[Maxim Muzafarov (Jira)]

Maxim Muzafarov created IGNITE-14572:


 Summary: Include metastorage into snapshot
 Key: IGNITE-14572
 URL: https://issues.apache.org/jira/browse/IGNITE-14572
 Project: Ignite
  Issue Type: Task
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
 Fix For: 2.11


Currently, only cache and cache groups with CacheType.USER included into a 
snapshot. We must also include into snapshot the metastorage data.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14571) Add RELEASE.md file to project.

[Andrey Mashenkov (Jira)]

Andrey Mashenkov created IGNITE-14571:
-

 Summary: Add RELEASE.md file to project.
 Key: IGNITE-14571
 URL: https://issues.apache.org/jira/browse/IGNITE-14571
 Project: Ignite
  Issue Type: Improvement
Reporter: Andrey Mashenkov
 Fix For: 3.0.0-alpha2


Let's describe release process and all action need to be taken for releasing 
Ignite into RELEASE.md file.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Static hierarchy in jmx tree

[Igor Akkuratov]

Is there anybody alive?

[jira] [Created] (IGNITE-14570) Ignite Extensions: Add default checkpoint methods to the IgnitePerformanceStatisticsHandler handler

[Amelchev Nikita (Jira)]

Amelchev Nikita created IGNITE-14570:


 Summary: Ignite Extensions: Add default checkpoint methods to the 
IgnitePerformanceStatisticsHandler handler
 Key: IGNITE-14570
 URL: https://issues.apache.org/jira/browse/IGNITE-14570
 Project: Ignite
  Issue Type: Task
Reporter: Amelchev Nikita
Assignee: Amelchev Nikita


Add default checkpoint methods to the IgnitePerformanceStatisticsHandler 
handler to fix compilation after 
[IGNITE-14385|https://issues.apache.org/jira/browse/IGNITE-14385].



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14569) Create data structures system view

[Ilya Kazakov (Jira)]

Ilya Kazakov created IGNITE-14569:
-

 Summary: Create data structures system view
 Key: IGNITE-14569
 URL: https://issues.apache.org/jira/browse/IGNITE-14569
 Project: Ignite
  Issue Type: Improvement
  Components: data structures
Affects Versions: 2.10
Reporter: Ilya Kazakov


It will be good to have an api to list all created data structures: latches, 
atomics and so on. So it could be a system view.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[CANCEL] [VOTE] Release Apache Ignite performance-statistics-ext, spring-data-all-ext and spring-tx-ext extensions 1.0.0 RC1

[Nikita Amelchev]

Folks,

Canceling due to absence of LICENSE and NOTICE files in binary package
and missing source package.

I have created the issue to fix it:
https://issues.apache.org/jira/browse/IGNITE-14568

-- 
Best wishes,
Amelchev Nikita

[jira] [Created] (IGNITE-14568) Add LICENSE and NOTICE files to release package of performance-statistics-ext extension

[Amelchev Nikita (Jira)]

Amelchev Nikita created IGNITE-14568:


 Summary: Add LICENSE and NOTICE files to release package of 
performance-statistics-ext extension
 Key: IGNITE-14568
 URL: https://issues.apache.org/jira/browse/IGNITE-14568
 Project: Ignite
  Issue Type: Task
Reporter: Amelchev Nikita
Assignee: Amelchev Nikita






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14567) Implement snapshot abstraction for RAFT client/server.

[Alexey Scherbakov (Jira)]

Alexey Scherbakov created IGNITE-14567:
--

 Summary: Implement snapshot abstraction for RAFT client/server.
 Key: IGNITE-14567
 URL: https://issues.apache.org/jira/browse/IGNITE-14567
 Project: Ignite
  Issue Type: Task
Reporter: Alexey Scherbakov
Assignee: Alexey Scherbakov
 Fix For: 3.0.0-alpha2


In addition to command processing [1] we need snapshot abstraction allowing for 
taking/restoring state machine state.

[1] org.apache.ignite.raft.client.service.RaftGroupCommandListener



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14566) Add information about checkpoints to the graphs of the performance statistics report

[Sergei Ryzhov (Jira)]

Sergei Ryzhov created IGNITE-14566:
--

 Summary: Add information about checkpoints to the graphs of the 
performance statistics report
 Key: IGNITE-14566
 URL: https://issues.apache.org/jira/browse/IGNITE-14566
 Project: Ignite
  Issue Type: Sub-task
Reporter: Sergei Ryzhov
Assignee: Sergei Ryzhov


Add information about checkpoints to the graphs of the performance statistics 
report.
Information should be in sections:
 - Cache operations statistics
 - Transactions statistics



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-14565) Add additional update counter logging for detect causes of AssertionError: LWM after HWM

[Maria Makedonskaya (Jira)]

Maria Makedonskaya created IGNITE-14565:
---

 Summary: Add additional update counter logging for detect causes 
of AssertionError: LWM after HWM
 Key: IGNITE-14565
 URL: https://issues.apache.org/jira/browse/IGNITE-14565
 Project: Ignite
  Issue Type: Bug
Reporter: Maria Makedonskaya
Assignee: Maria Makedonskaya






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [VOTE][EXTENSION] Release Apache Ignite performance-statistics-ext, spring-data-all-ext and spring-tx-ext extensions 1.0.0 RC1

[Ivan Daschinsky]

-1 From me. There is an absence of NOTICE and LICENSE files in binary
package. Also, there is no source package. These is a violation of apache
release policy [1]
[1] https://www.apache.org/legal/release-policy.html

чт, 15 апр. 2021 г. в 23:23, Nikita Amelchev :

> According to ASF release policy [1] non-PMC committers can sign artifacts:
>
> > all artifacts placed in their directory must be signed by a committer,
> preferably by a PMC member.
>
> [1] https://www.apache.org/legal/release-policy.html
>
> чт, 15 апр. 2021 г. в 23:05, Dmitriy Pavlov :
> >
> > My best guess that since PMCs have a binding vote in voting in release, a
> > PMC member should sign binaries as well. And I suppose that in the past
> > only PMC members were signing the release.
> >
> > Meanwhile, https://infra.apache.org/release-signing.html does not
> contain
> > any mention of PMC role and only committers are mentioned there. It
> > might be not an answer, since a lot of projects have PMC=Committer and
> just
> > one election.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > чт, 15 апр. 2021 г. в 22:05, Ivan Daschinsky :
> >
> > > I'm sorry, but is it OK, that artifacts are signed with signature of
> > > non-PMC?
> > >
> > > чт, 15 апр. 2021 г. в 19:26, Nikita Amelchev :
> > >
> > > > Dear Ignite Community,
> > > >
> > > > I have uploaded a release candidate of the following extension
> modules:
> > > >
> > > > performance-statistics-ext
> > > > spring-data-ext
> > > > spring-data-2.0-ext
> > > > spring-data-2.2-ext
> > > > spring-data-commons
> > > > spring-tx-ext
> > > >
> > > > The release candidate of the performance-statistics-ext extension:
> > > >
> > > >
> > >
> https://dist.apache.org/repos/dist/dev/ignite/ignite-performance-statistics-ext/1.0.0-rc1/
> > > >
> > > > The following staging can be used for testing:
> > > >
> https://repository.apache.org/content/repositories/orgapacheignite-1509
> > > >
> > > > Tags were created:
> > > >
> > > > ignite-performance-statistics-ext-1.0.0-rc1
> > > >
> > > >
> > >
> https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=commit;h=b992d9758278c38e93b375b08e4052954744a436
> > > >
> > > > ignite-spring-data-ext-1.0.0-rc1
> > > > ignite-spring-data-2.2-ext-1.0.0-rc1
> > > > ignite-spring-data-2.0-ext-1.0.0-rc1
> > > > ignite-spring-data-commons-1.0.0-rc1
> > > > ignite-spring-data-all-ext-1.0.0-rc1
> > > >
> > > >
> > >
> https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=commit;h=277ca95f6472d8bd46d906e70ba1a312d36dadb0
> > > >
> > > > ignite-spring-tx-ext-1.0.0-rc1
> > > >
> > > >
> > >
> https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=commit;h=55a3ae9e011ba48796847a33481842f154f0febb
> > > >
> > > > RELEASE NOTES:
> > > >
> > > >
> > >
> https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=blob;f=RELEASE_NOTES.txt;h=22f8d665c194ba2dfa6167354d97ad53d5ef206f;hb=c8de80ee14d1fb76d6cbb0b18513bb70b499c3cb
> > > >
> > > > DOCUMENTATION:
> > > > Documentation of listed extensions was updated in the following
> issues:
> > > >
> > > >
> > >
> https://issues.apache.org/jira/issues/?filter=-1=key%20in%20(IGNITE-14417%2CIGNITE-14398%2CIGNITE-14397%2CIGNITE-14493)
> > > >
> > > > The vote is formal, see voting guidelines
> > > > https://www.apache.org/foundation/voting.html
> > > >
> > > > +1 - to accept all the Apache Ignite performance-statistics-ext,
> > > > spring-data-all-ext and spring-tx-ext extensions 1.0.0-rc1 listed in
> > > > the thread
> > > > 0 - don't care either way
> > > > -1 - DO NOT accept either of the Apache Ignite
> > > > performance-statistics-ext, spring-data-all-ext and spring-tx-ext
> > > > extensions 1.0.0-rc1 (explain why)
> > > >
> > > > The vote will hold for 72 hours and will end on April 18 2021 17:00
> UTC
> > > >
> > > >
> > >
> https://www.timeanddate.com/countdown/generic?iso=20210418T17=1440=cursive
> > > >
> > > > --
> > > > Best wishes,
> > > > Amelchev Nikita
> > > >
> > >
> > >
> > > --
> > > Sincerely yours, Ivan Daschinskiy
> > >
>
>
>
> --
> Best wishes,
> Amelchev Nikita
>


-- 
Sincerely yours, Ivan Daschinskiy