Re: [ANNOUNCE] Apache Ignite 2.0.0 Released

[Denis Magda]

Dear Ignite contributors and committers, thanks for making this happen! Dear 
Ignite users, thanks for keep using and trusting Ignite!

That worth our efforts ;)

Just in a case here is a link to the blog mentioned below and Apache Ignite 2.0 
webinar:
- Blog: https://blogs.apache.org/ignite/entry/apache-ignite-2-0-redesigned
- Webinar: https://ignite.apache.org/releases/2.0.0/release_notes.html

Please share the news, don’t be shy - boast about this:
https://twitter.com/ApacheIgnite/status/860590282374500353

—
Denis

> On May 5, 2017, at 1:13 PM, Denis Magda  wrote:
> 
> The Apache Ignite Community is pleased to announce the release of Apache 
> Ignite 2.0.0.
> 
> Apache Ignite In-Memory Data Fabric [1] is a high-performance, integrated and 
> distributed in-memory platform for computing and transacting on large-scale 
> data sets in real-time, orders of magnitude faster than possible with 
> traditional disk-based or flash-based technologies.
> 
> The Fabric is a collection of independent and well integrated components some 
> of which are the following:  
> - Data Grid
> - SQL Grid
> - Compute Grid
> - Service Grid
> - Machine Learning Grid (NEW!)
> 
> This release incorporates tremendous changes that shifted Ignite 2.0 to the 
> next level. The whole off-heap memory architecture was redesigned from 
> scratch and, going forward, Ignite can be easily integrated with Flash and 
> SSD drives (stay tuned!). SQL Grid has been enriched with Data Definition 
> Language support. A completely new component was added to the fabric - 
> Machine Learning Grid. We provided integrations with RocketMQ and Spring 
> Data, updated Hibernate integration, introduced a plugin system for .NET and 
> found out how to execute C++ code on remote node, and many more...
> 
> Get more details from this blog post: 
> https://blogs.apache.org/ignite/entry/apache-ignite-2-0-redesigned
> 
> The full list of the changes can be found here [2].
> 
> Please visit this page if you’re ready to try the release out:
> https://ignite.apache.org/download.cgi
> 
> Please let us know [3] if you encounter any problems.
> 
> Regards,
> 
> The Apache Ignite Community
> 
> [1] https://ignite.apache.org
> [2] https://ignite.apache.org/releases/2.0.0/release_notes.html
> [3] https://ignite.apache.org/community/resources.html#ask

[ANNOUNCE] Apache Ignite 2.0.0 Released

[Denis Magda]

The Apache Ignite Community is pleased to announce the release of Apache Ignite 
2.0.0.

Apache Ignite In-Memory Data Fabric [1] is a high-performance, integrated and 
distributed in-memory platform for computing and transacting on large-scale 
data sets in real-time, orders of magnitude faster than possible with 
traditional disk-based or flash-based technologies.

The Fabric is a collection of independent and well integrated components some 
of which are the following:  
- Data Grid
- SQL Grid
- Compute Grid
- Service Grid
- Machine Learning Grid (NEW!)

This release incorporates tremendous changes that shifted Ignite 2.0 to the 
next level. The whole off-heap memory architecture was redesigned from scratch 
and, going forward, Ignite can be easily integrated with Flash and SSD drives 
(stay tuned!). SQL Grid has been enriched with Data Definition Language 
support. A completely new component was added to the fabric - Machine Learning 
Grid. We provided integrations with RocketMQ and Spring Data, updated Hibernate 
integration, introduced a plugin system for .NET and found out how to execute 
C++ code on remote node, and many more...

Get more details from this blog post: 
https://blogs.apache.org/ignite/entry/apache-ignite-2-0-redesigned

The full list of the changes can be found here [2].

Please visit this page if you’re ready to try the release out:
https://ignite.apache.org/download.cgi

Please let us know [3] if you encounter any problems.

Regards,

The Apache Ignite Community

[1] https://ignite.apache.org
[2] https://ignite.apache.org/releases/2.0.0/release_notes.html
[3] https://ignite.apache.org/community/resources.html#ask

Re: Add ability to enable and disable rebalancing per-node

[npordash]

I can outline a use-case I have which may help define requirements for this
task. For context, I was originally going to try and address the below
use-case by disabling automatic rebalancing on a per-cache basis and use a
cluster-wide task to orchestrate manual rebalancing; however, this issue
sounds like it may provide a better approach.

I have caches setup for the sole purpose of routing data to nodes via a Data
Streamer. The logic in the streamer is simply to access a plugin on the data
node which exposes a processing pipeline and runs the received cache entries
through it. The data in this case is monitoring related and there is one
cache (or logical stream) per data type (f.e. logs, events, metrics).

The pipeline is composed of N services which are deployed as node singletons
and have a service filter which targets a particular cache. These services
can be deployed and un-deployed as processing requirements change or bugs
are fixed without requiring clients to know or care about it.

The catch here is that when nodes are added I don't want map partitions to
rebalance to a new node until I know all of the necessary services are
running, otherwise we may have a small window where data is processed
through a pipeline that isn't completely initialized yet which would result
in a data quality issue. Alternatively, I could have the pipeline raise an
error which would cause the streamer to retry, but I'd like this to be
handled more gracefully, if possible.

In addition, it will probably be the case were these caches eventually have
node filters so that we can isolate resources for these streams across
different computes. This means that, for example, if we add a node only for
metrics then deferring rebalancing should ideally only impact caches that
would get assigned to that node.

Going even further... so far we've talked about one cache which is used just
for streaming, but at least one of the services would create its own set of
caches as an in-memory storage layer which maintains an inverted index and
time series data for elements coming through the stream. The storage caches
in this case would only exist on nodes where the stream cache is and most of
the write activity to these caches would be local since they would use the
same affinity as the stream cache (if most writes were remote this wouldn't
scale well). So... these caches would need to rebalance at the same time in
order to minimize the possibility of additional network calls.

The main concern I have is how to avoid the race condition of another node
joining the topology _after_ it has been determined rebalancing should
happen, but _before_ rebalancing is triggered. If this is controlled on a
per-node (+cache) basis - as the ticket describes - it's probably a
non-issue, but it's definitely an issue if it's only on a per-cache basis.

-Nick



--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/Add-ability-to-enable-and-disable-rebalancing-per-node-tp17494p17529.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

Re: Ignite Visor issue with 2.0

[Rishi Yagnik]

Yes this is the issue on my side, sir.

Please ignore it.

On Fri, May 5, 2017 at 12:40 PM, Denis Magda  wrote:

> Seems the issue was on Rishi’s side:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-
> 0-visor-issue-tp12460p12461.html  70518.x6.nabble.com/Ignite-2-0-visor-issue-tp12460p12461.html>
>
> —
> Denis
>
> > On May 5, 2017, at 10:26 AM, Denis Magda  wrote:
> >
> > Please share logs, command you’re executing and the configuration of
> your cluster.
> >
> > *Alex K.*, please keep an eye on this.
> >
> > —
> > Denis
> >
> >> On May 5, 2017, at 9:49 AM, Rishi Yagnik  wrote:
> >>
> >> I am seeing some weird issue with Ignite 2.0
> >>
> >> I cant see any stats on visor console, it s always empty.
> >>
> >> Did you all ever see this issue ?
> >>
> >> Thanks,
> >> Rishi
> >
>
>


-- 
Rishi Yagnik

[GitHub] ignite pull request #1916: IGNITE-4509: send unicast sql request when partit...

[skalashnikov]

GitHub user skalashnikov opened a pull request:

https://github.com/apache/ignite/pull/1916

IGNITE-4509: send unicast sql request when partition can be deduced f…

…rom the query

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-4509

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1916.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1916


commit 4a1768d28550286d69134ff62ee29994a0faa188
Author: skalashnikov 
Date:   2017-05-04T11:42:40Z

IGNITE-4509: send unicast sql request when partition can be deduced from 
the query




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Apache Ignite 2.0 Documentation

[Denis Magda]

All the examples work fine taking the libs from Maven Central. Agree with 
Alexey that it can take some time while 3rd party sites like [1] get synched up 
with Maven Central. In any case, I’ll put this on my radar.

[1] https://mvnrepository.com/artifact/org.apache.ignite/ignite-core 


—
Denis

> On May 5, 2017, at 9:50 AM, Rishi Yagnik  wrote:
> 
> Thank you Alexey..
> 
> On Fri, May 5, 2017 at 10:49 AM, Alexey Kuznetsov 
> wrote:
> 
>> Rishi,
>> 
>> May be not all mirrors are updated yet?
>> On [1] I see ignite-2.0 and can download jars from [2].
>> 
>> [1] http://search.maven.org
>> [2] https://repo1.maven.org/maven2/org/apache/ignite/ignite-core/2.0.0/
>> 
>> On Fri, May 5, 2017 at 10:22 PM, Rishi Yagnik 
>> wrote:
>> 
>>> I tried upgrading Ignite 2.0 but cant find ignite libs on maven
>> repository.
>>> 
>>> https://mvnrepository.com/artifact/org.apache.ignite/ignite-core
>>> 
>>> 
>>> 
>> --
>> Alexey Kuznetsov
>> 
> 
> 
> 
> -- 
> Rishi Yagnik

Re: Ignite Visor issue with 2.0

[Denis Magda]

Seems the issue was on Rishi’s side:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-0-visor-issue-tp12460p12461.html
 


—
Denis

> On May 5, 2017, at 10:26 AM, Denis Magda  wrote:
> 
> Please share logs, command you’re executing and the configuration of your 
> cluster. 
> 
> *Alex K.*, please keep an eye on this.
> 
> —
> Denis
> 
>> On May 5, 2017, at 9:49 AM, Rishi Yagnik  wrote:
>> 
>> I am seeing some weird issue with Ignite 2.0
>> 
>> I cant see any stats on visor console, it s always empty.
>> 
>> Did you all ever see this issue ?
>> 
>> Thanks,
>> Rishi
> 

Re: BinaryObjectImpl.deserializeValue with specific ClassLoader

[npordash]

Thanks Denis!



--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/Re-BinaryObjectImpl-deserializeValue-with-specific-ClassLoader-tp17126p17524.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

Re: New version of Web Console released.

[Prachi Garg]

Tom, Denis

I can blog about Ignite Web Console's multi-cluster support.

-Prachi

On Fri, May 5, 2017 at 10:24 AM, Denis Magda  wrote:

> These is awesome news! Thanks Alex.
>
> Do you mind writing a blog post about the release sharing some thought on
> the multi-cluster support? [1]
> Is there anyone else who can take over this?
>
> [1] https://apacheignite-tools.readme.io/docs/multi-cluster-support
>
> —
> Denis
>
> On May 5, 2017, at 5:38 AM, Alexey Kuznetsov 
> wrote:
>
> Igniters!
>
> I'd like to announce that we just pushed new version of Ignite Web Console to
> master branch
>  and redeployed the new version on https://console.gridgain.com where you
> can give it a try right a way.
>
> NOTE 1: You will need to download new version of web-agent.
> NOTE 2: You may need to refresh page (F5 or Ctrl+R) in order to reload Web
>  Console.
>
> What's new:
>
>   * Multi-cluster support (see: https://apacheignite-tools.
> readme.io/docs/multi-cluster-support).
>   * Added support for "Kubernetes - IP finder" on Cluster Configuration
> screen.
>   * Improved import metadata from RDBMS - added support for table aliases.
>   * Many minor improvements and bugfixes.
>
> Stay tuned for updates!
>
> ---
> Alexey Kuznetsov
>
>
>

Re: Ignite Visor issue with 2.0

[Denis Magda]

Please share logs, command you’re executing and the configuration of your 
cluster. 

*Alex K.*, please keep an eye on this.

—
Denis

> On May 5, 2017, at 9:49 AM, Rishi Yagnik  wrote:
> 
> I am seeing some weird issue with Ignite 2.0
> 
> I cant see any stats on visor console, it s always empty.
> 
> Did you all ever see this issue ?
> 
> Thanks,
> Rishi

Re: New version of Web Console released.

[Denis Magda]

These is awesome news! Thanks Alex.

Do you mind writing a blog post about the release sharing some thought on the 
multi-cluster support? [1] 
Is there anyone else who can take over this?

[1] https://apacheignite-tools.readme.io/docs/multi-cluster-support 


—
Denis

> On May 5, 2017, at 5:38 AM, Alexey Kuznetsov  wrote:
> 
> Igniters!
> 
> I'd like to announce that we just pushed new version of Ignite Web Console to 
> master branch
>  and redeployed the new version on https://console.gridgain.com 
>  where you can give it a try right a way.
> 
> NOTE 1: You will need to download new version of web-agent.
> NOTE 2: You may need to refresh page (F5 or Ctrl+R) in order to reload Web 
> Console.
> 
> What's new:
> 
>   * Multi-cluster support (see: 
> https://apacheignite-tools.readme.io/docs/multi-cluster-support 
> ).
>   * Added support for "Kubernetes - IP finder" on Cluster Configuration 
> screen. 
>   * Improved import metadata from RDBMS - added support for table aliases.
>   * Many minor improvements and bugfixes.
> 
> Stay tuned for updates!
> 
> --- 
> Alexey Kuznetsov

Re: Apache Ignite 2.0 Documentation

[Rishi Yagnik]

Thank you Alexey..

On Fri, May 5, 2017 at 10:49 AM, Alexey Kuznetsov 
wrote:

> Rishi,
>
> May be not all mirrors are updated yet?
> On [1] I see ignite-2.0 and can download jars from [2].
>
> [1] http://search.maven.org
> [2] https://repo1.maven.org/maven2/org/apache/ignite/ignite-core/2.0.0/
>
> On Fri, May 5, 2017 at 10:22 PM, Rishi Yagnik 
> wrote:
>
> > I tried upgrading Ignite 2.0 but cant find ignite libs on maven
> repository.
> >
> > https://mvnrepository.com/artifact/org.apache.ignite/ignite-core
> >
> >
> >
> --
> Alexey Kuznetsov
>



-- 
Rishi Yagnik

[jira] [Created] (IGNITE-5178) Simplify ML Grid build and release process

[Denis Magda (JIRA)]

Denis Magda created IGNITE-5178:
---

 Summary: Simplify ML Grid build and release process
 Key: IGNITE-5178
 URL: https://issues.apache.org/jira/browse/IGNITE-5178
 Project: Ignite
  Issue Type: Task
Affects Versions: 2.0
Reporter: Denis Magda
Assignee: Yury Babak
Priority: Critical
 Fix For: 2.1


ML component is Java 8 based which significantly complicated Apache Ignite 
build and release procedure. We need to try to find a way to simplify the 
release of the module in 2.1.

Has to be discussed with [~avinogradov], [~skozlov] and [~dmagda]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Apache Ignite 2.0 Documentation

[Alexey Kuznetsov]

Rishi,

May be not all mirrors are updated yet?
On [1] I see ignite-2.0 and can download jars from [2].

[1] http://search.maven.org
[2] https://repo1.maven.org/maven2/org/apache/ignite/ignite-core/2.0.0/

On Fri, May 5, 2017 at 10:22 PM, Rishi Yagnik  wrote:

> I tried upgrading Ignite 2.0 but cant find ignite libs on maven repository.
>
> https://mvnrepository.com/artifact/org.apache.ignite/ignite-core
>
>
>
-- 
Alexey Kuznetsov

Re: Apache Ignite 2.0 Documentation

[Rishi Yagnik]

I tried upgrading Ignite 2.0 but cant find ignite libs on maven repository.

https://mvnrepository.com/artifact/org.apache.ignite/ignite-core



On Thu, May 4, 2017 at 1:43 PM, Denis Magda  wrote:

> Evgeniy,
>
> Thanks a lot for pointing out to this! I’ve fixed the docs.
>
> —
> Denis
>
> > On May 3, 2017, at 11:56 PM, Evgeniy Ignatiev <
> yevgeniy.ignat...@gmail.com> wrote:
> >
> > Hello.
> >
> > On a "Resource Injection" page LoadBalancerResource line states that it
> injects IgniteLogger - seems to be an issue with docs. Also on
> "Asynchronous Support" in "Closures Execution and Thread Pools" section
> there seems to be some typos/missed words:
> >
> > asynchronous operation has been *comp* completed
> > Otherwise, the closure will be  asynchronously upon the
> operation completion
> >
> > On 5/4/2017 3:07 AM, Denis Magda wrote:
> >> Well, so many stuff that I eventually forgot about RocketMQ
> integration, sorry Roman ;)
> >> Just released the latest doc: https://apacheignite-mix.
> readme.io/docs/rocketmq-streamer
> >>
> >> —
> >> Denis
> >>
> >>> On May 3, 2017, at 4:00 PM, Denis Magda  wrote:
> >>>
> >>> Igniters, thanks to all of you who helped documenting 2.0 features! We
> could complete the documentation just in time and I’ve just released it.
> >>>
> >>> Just to give you a sense on how many things were added to Ignite 2.0
> here is a list of completely new or significantly updated docs:
> >>> * Page memory: https://apacheignite.readme.io/docs/page-memory
> >>> * Memory & Cache Metrics: https://apacheignite.readme.
> io/docs/memory-and-cache-metrics
> >>> * Eviction policies: https://apacheignite.readme.io/docs/evictions
> >>>
> >>> * DDL: https://apacheignite.readme.io/docs/distributed-ddl
> >>>
> >>> * Machine Learning Grid (beta): https://apacheignite.readme.
> io/docs/machine-learning
> >>>
> >>> * Renewed Async API: https://apacheignite.readme.
> io/docs/async-support
> >>> * Apache Ignite thread pools including the new custom one:
> https://apacheignite.readme.io/docs/thread-pools
> >>>
> >>> * .NET Plugins: https://apacheignite-net.readme.io/docs/plugins
> >>>
> >>> * C++ Continuous Queries remote filters: https://apacheignite-cpp.
> readme.io/docs/continuous-queries#section-remote-filter
> >>>
> >>> * Spring Data Integration: https://apacheignite-mix.
> readme.io/v2.0/docs/spring-data
> >>>
> >>> And, for the first time we prepare a migration guide for you dear
> users: https://apacheignite.readme.io/docs/apache-ignite-20
> >>>
> >>> —
> >>> Denis
> >>>
>  On Apr 13, 2017, at 6:46 PM, Dmitriy Setrakyan 
> wrote:
> 
>  Denis, thanks for tracking the documentation changes! This is the
> part that
>  usually gets missed by the community.
> 
>  On Thu, Apr 13, 2017 at 12:46 PM, Denis Magda 
> wrote:
> 
> > Folks,
> >
> > I’ve prepared a list of changes that have to be documented before the
> > public release of 2.0:
> > https://issues.apache.org/jira/browse/IGNITE-4960
> >
> > That’s an impressive release and there are some many things to
> document.
> > Actually, I’ll try to document the biggest part contacting
> contributors in
> > person but still need a help from some of you:
> >
> > * Nikita, Oleg (Machine Learning): https://issues.apache.org/
> > jira/browse/IGNITE-4964
> > * Vovan or Alex P. (DDL indexing statements):
> https://issues.apache.org/
> > jira/browse/IGNITE-4967
> > * Vovan (custom thread pools): https://issues.apache.org/
> > jira/browse/IGNITE-4969
> > * Vovan or Taras (next gen async API): https://issues.apache.org/
> > jira/browse/IGNITE-4972
> > * Val (Hibernate improvements): https://issues.apache.org/
> > jira/browse/IGNITE-4972
> > * Pavel (.NET plugin system): https://issues.apache.org/
> > jira/browse/IGNITE-4973
> > * Pavel (.NET dynamically registered classes):
> https://issues.apache.org/
> > jira/browse/IGNITE-4974
> > * Igor Sapego (C++ CQ remote filters): https://issues.apache.org/
> > jira/browse/IGNITE-4976
> >
> > Let’s pull together and accomplish this part of the release together.
> >
> > —
> > Denis
> >
> >
> >
>
>


-- 
Rishi Yagnik

[GitHub] ignite pull request #1915: IGNITE-5150: Allocated memory pages count is inco...

[glukos]

GitHub user glukos opened a pull request:

https://github.com/apache/ignite/pull/1915

IGNITE-5150: Allocated memory pages count is incorrect during load test



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-5150

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1915.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1915


commit cd3959e599cb2776540c053c1d1053c5ee8c6883
Author: Ivan Rakov 
Date:   2017-05-05T15:12:05Z

IGNITE-5150: Allocated memory pages count is incorrect during load test




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1906: Ignite 4991

[rfqu]

GitHub user rfqu reopened a pull request:

https://github.com/apache/ignite/pull/1906

Ignite 4991

issue IGNITE-4991 fixed

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rfqu/ignite ignite-4991

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1906.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1906


commit d6e7050280817b4705302346e170a1809a3d1a91
Author: Ivan Rakov 
Date:   2017-05-03T08:24:01Z

IGNITE-5134: Fixed ClassCastException in IgniteCacheDatabaseSharedManager. 
This closes #1895.

commit ff08c8e09033a1a703aae602c36a21565fbae606
Author: Anton Vinogradov 
Date:   2017-05-03T09:49:18Z

Hibernate module deploy fix

commit af3bec468ebd82ccaba850843925b5709efe78d7
Author: rfqu 
Date:   2017-05-04T10:08:27Z

issue fixed: IGNITE-4991

commit 9b897fcea2ec61a49f80b88d543bde6a0d0d5bde
Author: rfqu 
Date:   2017-05-04T10:08:27Z

issue fixed: IGNITE-4991

commit 5f0673ff10991f6705076c2f9d83ea78e2570eaf
Author: rfqu 
Date:   2017-05-05T14:18:34Z

Merge branch 'ignite-4991' of https://github.com/rfqu/ignite into 
ignite-2.0.1-IGNITE-4991

# Conflicts:
#   
modules/core/src/test/java/org/apache/ignite/internal/IgniteKernalLogTest.java




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1906: Ignite 4991

[rfqu]

Github user rfqu closed the pull request at:

https://github.com/apache/ignite/pull/1906


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-5177) Failed javadoc generation for web-agent

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-5177:


 Summary: Failed javadoc generation for web-agent
 Key: IGNITE-5177
 URL: https://issues.apache.org/jira/browse/IGNITE-5177
 Project: Ignite
  Issue Type: Bug
Reporter: Oleg Ostanin
Assignee: Andrey Novikov
 Fix For: 2.1


[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-antrun-plugin:1.7:run 
(javadoc-postprocessing-new) on project apache-ignite: An Ant BuildException 
has occured: Execution failed due to: Class doesn't have description in file: 
/home/oostanin/gg/incubator-ignite/target/javadoc/core/org/apache/ignite/console/agent/handlers/ClusterListener.html
[ERROR] Class doesn't have description in file: 
/home/oostanin/gg/incubator-ignite/target/javadoc/core/org/apache/ignite/console/agent/handlers/DemoListener.html
[ERROR] Class doesn't have description in file: 
/home/oostanin/gg/incubator-ignite/target/javadoc/core/org/apache/ignite/console/agent/rest/RestExecutor.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] ignite pull request #1908: IGNITE-5169

[devozerov]

Github user devozerov closed the pull request at:

https://github.com/apache/ignite/pull/1908


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1914: IGNITE-5151: Add a warning when offheap eviction ...

[shroman]

GitHub user shroman opened a pull request:

https://github.com/apache/ignite/pull/1914

IGNITE-5151: Add a warning when offheap eviction occurs.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/shroman/ignite IGNITE-5151

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1914.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1914


commit d4eca1286fd700c65db0d3816322fa2907a470bd
Author: shroman 
Date:   2017-05-05T13:36:16Z

IGNITE-5151: Add a warning when offheap eviction occurs.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-5176) JDBC Driver: implement query execution for thin jdbc driver based on common odbc/jdbc protocol

[Taras Ledkov (JIRA)]

Taras Ledkov created IGNITE-5176:


 Summary: JDBC Driver: implement query execution for thin jdbc 
driver based on common odbc/jdbc protocol
 Key: IGNITE-5176
 URL: https://issues.apache.org/jira/browse/IGNITE-5176
 Project: Ignite
  Issue Type: Task
  Components: jdbc-driver
Affects Versions: 2.0
Reporter: Taras Ledkov
Assignee: Taras Ledkov
 Fix For: 2.1


Implementation query execution & fetch results for thin JDBC driver over ODBC 
protocol.





--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

New version of Web Console released.

[Alexey Kuznetsov]

Igniters!

I'd like to announce that we just pushed new version of Ignite Web Console to
master branch
 and redeployed the new version on https://console.gridgain.com where you
can give it a try right a way.

NOTE 1: You will need to download new version of web-agent.
NOTE 2: You may need to refresh page (F5 or Ctrl+R) in order to reload Web
Console.

What's new:

  * Multi-cluster support (see:
https://apacheignite-tools.readme.io/docs/multi-cluster-support).
  * Added support for "Kubernetes - IP finder" on Cluster Configuration
screen.
  * Improved import metadata from RDBMS - added support for table aliases.
  * Many minor improvements and bugfixes.

Stay tuned for updates!

---
Alexey Kuznetsov

[GitHub] ignite pull request #1912: IGNITE-5163 JDBC Driver: thin jdbc driver is base...

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

https://github.com/apache/ignite/pull/1912

IGNITE-5163  JDBC Driver: thin jdbc driver is based on pure TCP protocol 
(handshake implementation)



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-5163

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1912.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1912


commit c7e215347e567f5c6c11954d932cfbb63743ec24
Author: tledkov-gridgain 
Date:   2017-05-04T14:59:38Z

IGNITE-5163 save the progress

commit b0023f87ab9f08063001bee77931ae9edc13487e
Author: tledkov-gridgain 
Date:   2017-05-05T12:03:08Z

IGNITE-5163 save the progress

commit fa9fee2a996f676f2a1c3371adaf0a35ce2810f7
Author: tledkov-gridgain 
Date:   2017-05-05T12:03:14Z

Merge branch '_master' into ignite-5163

commit dca4546b82547f1eef97e7bd1f3254914d3b5055
Author: tledkov-gridgain 
Date:   2017-05-05T12:06:04Z

Merge branch '_master' into ignite-5163

commit db57be2da1beddc91df301033386f2a97ec578f2
Author: tledkov-gridgain 
Date:   2017-05-05T12:11:29Z

IGNITE-5163: fix after merge




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1905: IGNITE-5128 Support queries for GridClientData

[tledkov-gridgain]

Github user tledkov-gridgain closed the pull request at:

https://github.com/apache/ignite/pull/1905


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

IGNITE-2671 Node cannot join topology when cache lock is held.

[ALEKSEY KUZNETSOV]

Hello Igntrs!
I would like to start working on
*https://issues.apache.org/jira/browse/IGNITE-2671
* if you don't mind.
-- 

*Best Regards,*

*Kuznetsov Aleksey*

[jira] [Created] (IGNITE-5175) Performance degradation using evictions in near-enabled caches

[Igor Seliverstov (JIRA)]

Igor Seliverstov created IGNITE-5175:


 Summary: Performance degradation using evictions in near-enabled 
caches
 Key: IGNITE-5175
 URL: https://issues.apache.org/jira/browse/IGNITE-5175
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.0
Reporter: Igor Seliverstov
Assignee: Ivan Rakov


Both RandomLruNearEnabledPageEvictionMultinodeTest.testPageEviction and 
Random2LruNearEnabledPageEvictionMultinodeTest.testPageEviction fail with 
timeout exceptions. 

Seems that the execution time (eviction operation) is non-linearly dependent on 
a count of elements in the cache (the more elements the longer the operation).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Hello

[Wuwei Lin]

Hi,  community!

I'm Wuwei Lin. I’d like to join the community and start contributing. My Jira 
id is vinx13.

Regards,
Wuwei

[GitHub] ignite pull request #1838: Ignite gg 11423 from20

[oleg-ostanin]

Github user oleg-ostanin closed the pull request at:

https://github.com/apache/ignite/pull/1838


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Add ability to enable and disable rebalancing per-node

[Sasha Belyak]

Hi,
I have jira ticket https://issues.apache.org/jira/browse/IGNITE-5061 with
subj and now I'm trying to understand partition exchange mechanism.
As far as I understand, task point is: it need when we have to grow cluster
(start few new nodes without partition exchange and enable exchange after
we completely get desired topology).
All nodes know actual partition topology, so partitions can stay unbalanced
for long time.
How I see solution:
1) Add in ignite MBean some flag enablePartitionExchange
2) Test it in GridDhtPartitionDemander.requestPartitions and complete
RebalanceFuture if partitionExchange is disabled
3) Somehow fire up force rebalance when flag change to true.
Does anybody see problems with this solution? Maybe we need to add
per-cache granularity or let system caches rebalance even if
enablePartitionExchange=false? Does we have some huge changes in progress,
which can conflict with it?

[GitHub] ignite pull request #1911: GridGain Professional 2.0.1

[devozerov]

GitHub user devozerov opened a pull request:

https://github.com/apache/ignite/pull/1911

GridGain Professional 2.0.1



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-2.0.1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1911.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1911


commit d6e7050280817b4705302346e170a1809a3d1a91
Author: Ivan Rakov 
Date:   2017-05-03T08:24:01Z

IGNITE-5134: Fixed ClassCastException in IgniteCacheDatabaseSharedManager. 
This closes #1895.

commit ff08c8e09033a1a703aae602c36a21565fbae606
Author: Anton Vinogradov 
Date:   2017-05-03T09:49:18Z

Hibernate module deploy fix

commit bc4735f7f5e3fe97aa5f30ef8bdf88e0749d6e2e
Author: Igor Sapego 
Date:   2017-05-03T15:12:49Z

IGNITE-5132: Fixed PutGet example.

(cherry picked from commit ed72663ff8e6b6f46d77c91471400ec1c9ff0dfa)




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request #1910: IGNITE-5174 client nodes filter func

[zstan]

GitHub user zstan opened a pull request:

https://github.com/apache/ignite/pull/1910

IGNITE-5174 client nodes filter func



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-5174

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/1910.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1910


commit 2185c173059db0615bfbb6b9d54ed92f5e1cb511
Author: Evgeny Stanilovskiy 
Date:   2017-05-05T06:50:04Z

IGNITE-5174 client nodes filter func




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-5174) Need to have opportunity to list only server nodes for specified topology version

[Stanilovsky Evgeny (JIRA)]

Stanilovsky Evgeny created IGNITE-5174:
--

 Summary: Need to have opportunity to list only server nodes for 
specified topology version
 Key: IGNITE-5174
 URL: https://issues.apache.org/jira/browse/IGNITE-5174
 Project: Ignite
  Issue Type: Bug
Reporter: Stanilovsky Evgeny
Assignee: Stanilovsky Evgeny
Priority: Minor
 Fix For: 2.1


Need to have common utility function which filters client nodes for specified 
topology version.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)