Re: No commits to Ignite website: migration from SVN to Git is in progress

[Ivan Pavlukhin]

Thank you!

Best regards,
Ivan Pavlukhin

вт, 7 апр. 2020 г. в 00:46, Denis Magda :
>
> The website is back to normal and serves the content from the Git
> repository's "master" branch:
> https://github.com/apache/ignite-website/blob/master
>
> -
> Denis
>
>
> On Mon, Apr 6, 2020 at 2:19 PM Denis Magda  wrote:
>
> > I'm checking with the INFRA. It's down for at least the last couple of
> > hours.
> >
> > -
> > Denis
> >
> >
> > On Mon, Apr 6, 2020 at 12:44 PM Ivan Pavlukhin 
> > wrote:
> >
> >> Denis,
> >>
> >> Is it expected that main website https://ignite.apache.org/ does not
> >> work now?
> >>
> >> Best regards,
> >> Ivan Pavlukhin
> >>
> >> сб, 4 апр. 2020 г. в 01:15, Denis Magda :
> >> >
> >> > Igniters,
> >> >
> >> > Please avoid any commits to the website repository until further notice.
> >> > We're in a process of the migration:
> >> > https://issues.apache.org/jira/browse/INFRA-20065
> >> >
> >> > -
> >> > Denis
> >>
> >

Re: Change Ignite download.cgi page to satisfy requirements

[Maxim Muzafarov]

Denis,

Since the Apache Ignite website has been updated and moved to git can
we proceed with changing the `download.cgi` page [2]?


[1] https://ignite.apache.org/download.cgi
[2] https://issues.apache.org/jira/browse/IGNITE-12775

On Sat, 28 Mar 2020 at 01:55, Denis Magda  wrote:
>
> Agreed,
>
> I'll ask INFRA to proceed with the Git migration first days next week.
> Please wait while the migration ends.
>
> -
> Denis
>
>
> On Fri, Mar 27, 2020 at 11:22 AM Maxim Muzafarov  wrote:
>
> > Denis,
> >
> > I think we can move to git first. I'll do the changes discussed above
> > by the end of the next week.
> >
> > On Fri, 27 Mar 2020 at 20:55, Denis Magda  wrote:
> > >
> > > Maxim,
> > >
> > > The new website is launched [1] and we can proceed with the changes
> > > discussed in this thread.
> > >
> > > Will you have time to implement those next week? If it's highly unlikely
> > > then I would request INFRA to move the website to Git first.
> > >
> > > [1]
> > >
> > http://apache-ignite-developers.2346864.n4.nabble.com/ANNOUNCEMENT-Ignite-New-Website-is-Live-td46730.html
> > >
> > > -
> > > Denis
> > >
> > >
> > > On Wed, Mar 25, 2020 at 9:47 AM Denis Magda  wrote:
> > >
> > > > Hi Maxim,
> > > >
> > > > Here is a ticket [1] where I've collected INFRA recommendations shared
> > in
> > > > an adjacent discussion thread. Please check it, add anything new you
> > heard
> > > > from them.
> > > >
> > > > Feel free to take over this task, appreciate your help. However, please
> > > > give me a couple of days to finish the merge of the new website to the
> > > > master branch. After that, you can update the downloads page and I'll
> > > > request INFRA to move the website to a Git repository. I'll send a note
> > > > here once the new website is released.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-12775
> > > >
> > > > -
> > > > Denis
> > > >
> > > >
> > > > On Wed, Mar 25, 2020 at 3:31 AM Maxim Muzafarov 
> > wrote:
> > > >
> > > >> Igniters,
> > > >>
> > > >>
> > > >> I've recently found that some of our releases were missed at the
> > > >> Apache announce mail list: 2.6.0 [4], 2.7.0 [5], 2.8.0 [3].
> > > >>
> > > >> I've contacted the Apache announce list moderators and got the
> > > >> requirements for our download page [6] (see the message below). I'm
> > > >> going to update the download page on the Apache Ignite website
> > > >> according to received instructions using these pages as an example [1]
> > > >> [2].
> > > >>
> > > >> WDYT?
> > > >>
> > > >>
> > > >> Denis,
> > > >>
> > > >> Do we have maintainer here or I can proceed with this by myself?
> > > >>
> > > >>
> > > >> >  >
> > > >>
> > > >> Sorry, but the download page does not meet the requirements.
> > > >>
> > > >> 1) There is no link to the KEYS file
> > > >> https://downloads.apache.org/ignite/KEYS
> > > >> This is necessary for validating downloaded artifacts
> > > >>
> > > >> 2) No description of how to validate downloads
> > > >>
> > > >> 3) There is a link to nightly builds.
> > > >> That is not allowed on a public download page, as the builds have not
> > been
> > > >> voted on.
> > > >>
> > > >> 4) The paragraph introducing the binary artifact says:
> > > >>
> > > >> "In order to verify the release, we recommend that you download the
> > > >> official source distribution and verify the signatures of the
> > downloaded
> > > >> files before opening them."
> > > >>
> > > >> This does not make sense in the binary section (it belongs in the
> > source
> > > >> section and/or needs rewording).
> > > >> Nor is there any description of how to perform the verification.
> > > >>
> > > >> Please correct the page and resubmit the announce when that has been
> > done.
> > > >>
> > > >> <  <
> > > >>
> > > >> [1] https://tika.apache.org/download.html
> > > >> [2] http://tomcat.apache.org/download-70.cgi
> > > >> [3]
> > > >>
> > http://mail-archives.us.apache.org/mod_mbox/www-announce/202003.mbox/browser
> > > >> [4]
> > > >>
> > http://mail-archives.us.apache.org/mod_mbox/www-announce/201806.mbox/browser
> > > >> [5]
> > > >>
> > http://mail-archives.us.apache.org/mod_mbox/www-announce/201812.mbox/browser
> > > >> [6] https://ignite.apache.org/download.cgi
> > > >>
> > > >
> >

Re: Ignite Website is Moved to Git

[Denis Magda]

A minor correction, that's the valid address, some of you got 404 by
opening the link shared before:
https://github.com/apache/ignite-website/

-
Denis


On Mon, Apr 6, 2020 at 2:48 PM Denis Magda  wrote:

> Just a heads-up for you that the website is now hosted in Git and serves
> the content from the "master" branch:
> https://github.com/apache/ignite-website/blob/master
>
> I'll update our "Website Development Instructions" in the next couple of
> days and send a note here.
>
> -
> Denis
>

Ignite 2.8 Webinar, April 8th - What's New in the Release

[Denis Magda]

Fellow Igniters,

There are so many changes that contributed to version 2.8, then even I, an
old-timer who is with the community for a while, underestimated how
startling this version turned out to be. Just finished my slides for the
webinar coming this Wednesday [1] and still finishing some code samples.

We're going to scratch the surface in some places and dig deeper in others.
That's a session for Ignite application developers and architects by
another application developer who is familiar with Ignite very well ;) Hope
Ignite contributors/committers who contributed most of the features join me
that day to see how this format goes and then we can schedule a series of
virtual meetups with live discussions and deep-dives.

[1] https://bit.ly/2XiW4zF

-
Denis

Ignite Website is Moved to Git

[Denis Magda]

Just a heads-up for you that the website is now hosted in Git and serves
the content from the "master" branch:
https://github.com/apache/ignite-website/blob/master

I'll update our "Website Development Instructions" in the next couple of
days and send a note here.

-
Denis

Re: No commits to Ignite website: migration from SVN to Git is in progress

[Denis Magda]

The website is back to normal and serves the content from the Git
repository's "master" branch:
https://github.com/apache/ignite-website/blob/master

-
Denis


On Mon, Apr 6, 2020 at 2:19 PM Denis Magda  wrote:

> I'm checking with the INFRA. It's down for at least the last couple of
> hours.
>
> -
> Denis
>
>
> On Mon, Apr 6, 2020 at 12:44 PM Ivan Pavlukhin 
> wrote:
>
>> Denis,
>>
>> Is it expected that main website https://ignite.apache.org/ does not
>> work now?
>>
>> Best regards,
>> Ivan Pavlukhin
>>
>> сб, 4 апр. 2020 г. в 01:15, Denis Magda :
>> >
>> > Igniters,
>> >
>> > Please avoid any commits to the website repository until further notice.
>> > We're in a process of the migration:
>> > https://issues.apache.org/jira/browse/INFRA-20065
>> >
>> > -
>> > Denis
>>
>

Re: No commits to Ignite website: migration from SVN to Git is in progress

[Denis Magda]

I'm checking with the INFRA. It's down for at least the last couple of
hours.

-
Denis


On Mon, Apr 6, 2020 at 12:44 PM Ivan Pavlukhin  wrote:

> Denis,
>
> Is it expected that main website https://ignite.apache.org/ does not work
> now?
>
> Best regards,
> Ivan Pavlukhin
>
> сб, 4 апр. 2020 г. в 01:15, Denis Magda :
> >
> > Igniters,
> >
> > Please avoid any commits to the website repository until further notice.
> > We're in a process of the migration:
> > https://issues.apache.org/jira/browse/INFRA-20065
> >
> > -
> > Denis
>

Re: No commits to Ignite website: migration from SVN to Git is in progress

[Ivan Pavlukhin]

Denis,

Is it expected that main website https://ignite.apache.org/ does not work now?

Best regards,
Ivan Pavlukhin

сб, 4 апр. 2020 г. в 01:15, Denis Magda :
>
> Igniters,
>
> Please avoid any commits to the website repository until further notice.
> We're in a process of the migration:
> https://issues.apache.org/jira/browse/INFRA-20065
>
> -
> Denis

Re: Joining Ignite ASF

[Ivan Pavlukhin]

Hello Semyon,

Welcome to Apache Ignite Community!

I added your account to the contributors list. Now you can assign
tickets to yourself. Do not hesitate to ask if you need any
assistance.

Please check this page out for commonly asked questions pertaining to
the contribution process https://ignite.apache.org/community/contribute.html
Consult "Pick a ticket" section if you have no ticket to start with.

Best regards,
Ivan Pavlukhin

пн, 6 апр. 2020 г. в 21:07, Данилов Семён :
>
> Hello!
> I would like to start contributing, could you please add me to contributors 
> list? My login for https://issues.apache.org/ is sdanilov.
>
> Kind regards,
> Semyon Danilov.

Joining Ignite ASF

[Данилов Семён]

Hello!
I would like to start contributing, could you please add me to contributors 
list? My login for https://issues.apache.org/ is sdanilov.
 
Kind regards,
Semyon Danilov.

[jira] [Created] (IGNITE-12869) Management API to kill a node that started user provided tasks and queries

[Sergei Ryzhov (Jira)]

Sergei Ryzhov created IGNITE-12869:
--

 Summary: Management API to kill a node that started user provided 
tasks and queries
 Key: IGNITE-12869
 URL: https://issues.apache.org/jira/browse/IGNITE-12869
 Project: Ignite
  Issue Type: Improvement
Reporter: Sergei Ryzhov
Assignee: Sergei Ryzhov


Ignite provides many API to deploy and execute user-provided code on the server 
nodes inside the same JVM as the Ignite process runs.
Ignite has many APIs that allocate many resources on the server nodes, also.
In case of some buggy code that consumes many system resources(CPU, RAM, flood 
network) or heavy query the whole cluster can become unstable.

We should provide to the cluster administrator the ability to stop the node 
that started the task if it did not may be cancel.

A new API should use the same identifier that is used in corresponding System 
View.




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

Re: Data vanished from cluster after INACTIVE/ACTIVE switch

[Вячеслав Коптилин]

Hello Vladimir,

> onto anolugous
>  @param forceDeactivation If {@code true}, cluster deactivation will be
forced. //Deactivation clears in-memory caches (without persistence)
including the system caches.
My idea was about providing a link to one place with a complete description
instead of copy

> We might include this fix in the last [1].
It is up to you, Vladimir.

Thanks,
S.



пт, 3 апр. 2020 г. в 15:42, Vladimir Steshin :

> Slava, hello.
>
>
> All right, since we have in public API several
>
> /* Deactivation clears in-memory caches (without persistence) including
> the system caches./
>
> We should change in the internals
>
> /@param forceDeactivation If {@code true}, cluster deactivation will
> be forced./
>
> onto anolugous
>
> /@param forceDeactivation If {@code true}, cluster deactivation will
> be forced. //Deactivation clears in-memory caches (without persistence)
> including the system caches./
>
> //
>
> We might include this fix in the last [1]. WDYT, can we proceed with [1]
> then ?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-12779
>
>
>
> 02.04.2020 19:58, Вячеслав Коптилин пишет:
> > Hi Vladimir,
> >
> >> There are about 15 places in inner logic with this description.
> >> I propose balance between code base size and comment completeness.
> > I agree with Iva and I also think that this approach is not so good.
> > Perhaps we can add just a link to the one method which will provide a
> > comprehensive description, something like as follows
> > @param forceDeactivation {@code true} if cluster deactivation should be
> > forced. Please take a look at {@link IgniteCluster#state(ClusterState
> > newState, boolean force)} for the details.
> >
> > What do you think?
> >
> > Thanks,
> > Slava.
> >
> > чт, 2 апр. 2020 г. в 18:47, Vladimir Steshin :
> >
> >> Ivan, hello.
> >>
> >> Thanks. I vote for keeping the comments as they are now :)
> >>
> >> Igniters, it seems we are agreed to merge [1]. And the ticked s to be
> >> reverted in future with new designed solution of keeping in-memory data
> >> after deactivation.
> >>
> >> Right?
> >>
> >>
> >> [1] https://issues.apache.org/jira/browse/IGNITE-12779
> >>
> >>
> >> 01.04.2020 20:20, Ivan Rakov пишет:
> >>> I don't think that making javadocs more descriptive can be considered
> as
> >>> harmful code base enlargement.
> >>> I'd recommend to extend the docs, but the last word is yours ;)
> >>>
> >>> On Tue, Mar 31, 2020 at 2:44 PM Vladimir Steshin 
> >> wrote:
>  Ivan, hi.
> 
>  I absolutely agree this particular description is not enough to see
> the
>  deactivation issue. I also vote for brief code.
> 
>  There are about 15 places in inner logic with this description. I
>  propose balance between code base size and comment completeness.
> 
>  Should we enlarge code even if we got several full descriptions?
> 
> 
>  30.03.2020 20:02, Ivan Rakov пишет:
> > Vladimir,
> >
> > @param forceDeactivation If {@code true}, cluster deactivation will
> be
> >> forced.
> > It's true that it's possible to infer semantics of forced
> deactivation
>  from
> > other parts of API. I just wanted to highlight that exactly this
> > description explains something that can be guessed by the parameter
> >> name.
> > I suppose to shorten the lookup path and shed a light on deactivation
> > semantics a bit:
> >
> >> @param forceDeactivation If {@code true}, cluster will be
> deactivated
>  even
> >> if running in-memory caches are present. All data in the
> corresponding
> >> caches will be vanished as a result.
> > Does this make sense?
> >
> > On Fri, Mar 27, 2020 at 12:00 PM Vladimir Steshin <
> vlads...@gmail.com>
> > wrote:
> >
> >> Ivan, hi.
> >>
> >>
> >> 1) >>> Is it correct? If we are on the same page, let's proceed this
> >> way
> >> It is correct.
> >>
> >>
> >> 2) - In many places in the code I can see the following javadoc
> >>
> >>>  @param forceDeactivation If {@code true}, cluster deactivation
> >> will
>  be
> >> forced.
> >>
> >> In the internal params/flags. You can also find /@see
> >> ClusterState#INACTIVE/ and full description with several public
> APIs (
> >> like /Ignite.active(boolean)/ ):
> >>
> >> //
> >>
> >> /* /
> >>
> >> //
> >>
> >> /* NOTE:/
> >>
> >> //
> >>
> >> /* Deactivation clears in-memory caches (without persistence)
> >> including
> >> the system caches./
> >>
> >> Should be enough. Is not?
> >>
> >>
> >> 27.03.2020 10:51, Ivan Rakov пишет:
> >>> Vladimir, Igniters,
> >>>
> >>> Let's emphasize our final plan.
> >>>
> >>> We are going to add --force flags that will be necessary to pass
> for
> >> a
> >>> deactivation if there are in-memory caches to:
> >>> 1) Rest API (already implemented in [1])
> >>> 2) Command line 

[jira] [Created] (IGNITE-12868) Calcite integration. LEFT, RIGHT join support.

[Igor Seliverstov (Jira)]

Igor Seliverstov created IGNITE-12868:
-

 Summary: Calcite integration. LEFT, RIGHT join support.
 Key: IGNITE-12868
 URL: https://issues.apache.org/jira/browse/IGNITE-12868
 Project: Ignite
  Issue Type: New Feature
Reporter: Igor Seliverstov






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

Possible concurrency bug in GridCacheLockImpl

[Zhenya Stanilovsky]

Ivan, i found that mentioned problem correctly highlighted, if we still not 
step on this rake, its probably due to some locks above, anyway it would be 
correct to fix this part. Are you fill the ticket ?
 
>
>
>--- Forwarded message ---
>From: "Ivan Daschinsky" < ivanda...@gmail.com >
>To:  dev@ignite.apache.org
>Cc:
>Subject: Re: Possible concurrency bug in GridCacheLockImpl
>Date: Fri, 03 Apr 2020 17:07:22 +0300
>
>Sorry, I meant not GridCacheLockImpl but CacheLockImpl.
>
>пт, 3 апр. 2020 г. в 17:04, Ivan Daschinskiy < ivanda...@gmail.com >:
>
>> Folks,
>>
>> Lurking through code, it seems I found some concurrency issue in subj.
>>
>> * This class contains two fields, volatile Thread lockedThread and
>> non-volatile int cntr (used for reentrancy)
>>
>> * private method incrementLockingCount() is called inside lock(). In this
>> method we perform volatile read in assert
>> (assert (lockedThread == null && cntr == 0) || (lockedThread ==
>> Thread.currentThread() && cntr > 0) then increment cntr;
>> * In method unlock(), we firstly decrement cntr and after that if cntr
>> equals to 0, performs volatile write to lockedThread.
>>
>> Suppose execution when asserts are enabled.
>>
>> T1 | T2
>>
>> ---
>> cntr = cntr - 1 (cntr == 0) |
>> lockedThread = null |
>> | lockedThread ==
>> null
>> && cntr == 0
>> | cntr = cntr + 1
>> (cntr
>> == 1)
>>
>>
>> There is a happens-before edge and we have strong guarantee that
>> reentrancy will works and cntr will definitely equals to 1;
>>
>> But if assertions are disabled, something can go wrong.
>>
>> Moreover, if assertions are disabled, we can allow other thread do obtain
>> lock even if our thread holds it.
>>
>> I think that this should be fixed, for example we can throw
>> IllegalStateException, as in unlock() method.
>>
>> WDYT?
>>
>> 
 
 
 
 

[jira] [Created] (IGNITE-12867) Python thin client: support for DB-API

[Stephen Darlington (Jira)]

Stephen Darlington created IGNITE-12867:
---

 Summary: Python thin client: support for DB-API
 Key: IGNITE-12867
 URL: https://issues.apache.org/jira/browse/IGNITE-12867
 Project: Ignite
  Issue Type: Improvement
  Components: python
Affects Versions: 2.8
Reporter: Stephen Darlington


Python has a database connection standard called [DB-API|http://example.com/]. 
It would make the Ignite Python thin client a lot more useful if it could use 
this in addition to its current Ignite-specific APIs. Implementing this would 
enable other Apache tools such as SuperSet and Airflow to connect to and use 
Ignite.



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

[jira] [Created] (IGNITE-12866) CQ fails due to CQ filter deserialization exception.

[PetrovMikhail (Jira)]

PetrovMikhail created IGNITE-12866:
--

 Summary: CQ fails due to CQ filter deserialization exception.
 Key: IGNITE-12866
 URL: https://issues.apache.org/jira/browse/IGNITE-12866
 Project: Ignite
  Issue Type: Bug
Reporter: PetrovMikhail


CQ fails if CQ filter deserialization exception occurred on a node that does 
not match the cache node filter in case cache node filter must be loaded via 
p2p.

Reproducer is linked as PR to the ticket.



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

Re: Contribution

[Ivan Pavlukhin]

Hello Nikita,

Welcome to Apache Ignite Community!

I added your account to the contributors list. Now you can assign
tickets to yourself. Do not hesitate to ask if you need any
assistance.

Please check this page out for commonly asked questions pertaining to
the contribution process https://ignite.apache.org/community/contribute.html

Best regards,
Ivan Pavlukhin

пн, 6 апр. 2020 г. в 12:25, Никита Алемаскин :
>
> Hello Ignite Community!
>
> My name is Nikita. I want to contribute to Apache Ignite and want to
> start with this issue - IGNITE-11494
> , my JIRA username
> is nikita_alemaskin. Any help on this will be appreciated.
>
> Thanks!

[jira] [Created] (IGNITE-12865) NPE occurs during CQ registration with cache node filter specified.

[PetrovMikhail (Jira)]

PetrovMikhail created IGNITE-12865:
--

 Summary: NPE occurs during CQ registration with cache node filter 
specified.
 Key: IGNITE-12865
 URL: https://issues.apache.org/jira/browse/IGNITE-12865
 Project: Ignite
  Issue Type: Bug
Reporter: PetrovMikhail


NPE occurs during CQ registration if 
1. Node that starts cache does not match cache node filter.
2. CQ is started on node that matches cache node filter.

Reproducer:
{code:java}
/** */
@Test
public void test() throws Exception {
IgniteEx filteredNode = startGrid(0);

IgniteEx cacheStoreNode = startGrid(1);

filteredNode.cluster().state(ClusterState.ACTIVE);

filteredNode.createCache(new CacheConfiguration<>(DEFAULT_CACHE_NAME)
.setNodeFilter(node -> 
!node.id().equals(filteredNode.localNode().id(;

ContinuousQuery qry = new ContinuousQuery<>();

qry.setLocalListener(evts -> {
//No-op.
});

cacheStoreNode.cache(DEFAULT_CACHE_NAME).query(qry);
}
{code}



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

Contribution

[Никита Алемаскин]

Hello Ignite Community!

My name is Nikita. I want to contribute to Apache Ignite and want to
start with this issue - IGNITE-11494
, my JIRA username
is nikita_alemaskin. Any help on this will be appreciated.

Thanks!

[jira] [Created] (IGNITE-12864) Calcite integration. UNION support.

[Igor Seliverstov (Jira)]

Igor Seliverstov created IGNITE-12864:
-

 Summary: Calcite integration. UNION support.
 Key: IGNITE-12864
 URL: https://issues.apache.org/jira/browse/IGNITE-12864
 Project: Ignite
  Issue Type: New Feature
Reporter: Igor Seliverstov






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