Re: Cassandra cache store [IGNITE-1371]

[Dmitriy Setrakyan]

Would be nice to get it into the next release.

On Wed, Feb 17, 2016 at 10:40 PM, irudyak  wrote:

> Actually the idea of PersistenceCallback interface looks good. I'll try to
> think how it's better to implement CassandraData class.
>
>
>
> --
> View this message in context:
> http://apache-ignite-developers.2346864.n4.nabble.com/Cassandra-cache-store-IGNITE-1371-tp6880p7436.html
> Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
>

[GitHub] ignite pull request: IGNITE-2416: TcpDiscoverySharedFsIpFinder to ...

[shroman]

GitHub user shroman opened a pull request:

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

IGNITE-2416: TcpDiscoverySharedFsIpFinder to work with IPv6 addresses.



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

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

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

https://github.com/apache/ignite/pull/495.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 #495


commit 96e0fa72b0b71a92621f30a737b2aafda4413d74
Author: shtykh_roman 
Date:   2016-02-18T06:58:41Z

IGNITE-2416: TcpDiscoverySharedFsIpFinder to work with IPv6 addresses.




---
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: Cassandra cache store [IGNITE-1371]

[irudyak]

Actually the idea of PersistenceCallback interface looks good. I'll try to
think how it's better to implement CassandraData class.



--
View this message in context: 
http://apache-ignite-developers.2346864.n4.nabble.com/Cassandra-cache-store-IGNITE-1371-tp6880p7436.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.

[jira] [Created] (IGNITE-2683) ClassLoader set in IgniteConfiguration is not always used

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-2683:


 Summary: ClassLoader set in IgniteConfiguration is not always used
 Key: IGNITE-2683
 URL: https://issues.apache.org/jira/browse/IGNITE-2683
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.5.0.final
Reporter: Semen Boikov
Assignee: Anton Vinogradov
Priority: Critical
 Fix For: 1.6


Now classloader set in IgniteConfiguration is not always passed to marshaller. 
Need review all placess where  Marshaller.unmarshal(InputStream in, @Nullable 
ClassLoader clsLdr) and Marshaller.unmarshal(byte[] arr, @Nullable ClassLoader 
clsLdr) are called.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Ignite .NET & C++ links on the main website

[Dmitriy Setrakyan]

Pavel, I think that the contributor(s) of the functionality have to add the
documentation. Otherwise, it will be very hard to do for the people not
deeply involved. Did you have something else in mind?

D.

On Wed, Feb 17, 2016 at 2:02 AM, Pavel Tupitsyn 
wrote:

> Igniters,
>
> We have released .NET & C++ support in 1.5, but there is not enough
> information about these on the main website:
>
> * No mentions in Features
> * Documentation submenu is inconsistent across different pages (Download
> page does not have .NET links in Documentation submenu for some reason)
> * "Ignite for .Net" should be "Ignite.NET"
> * API docs and readme.io docs are in different places, which is confusing
>
> Any thoughts on how to improve the situation?
>
> Thanks,
>
> --
> --
> Pavel Tupitsyn
> GridGain Systems, Inc.
> www.gridgain.com
>

Re: About issue 1661

[Dmitriy Setrakyan]

I linked IGNITE-2610 and IGNITE-1661 in Jira. Let’s process them together.

On Wed, Feb 17, 2016 at 12:58 PM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:

> Yes, from the description it looks related to IGNITE-2610. I will check the
> test attached to the IGNITE-1661 once I finish the fix for IGNITE-2610.
>

[jira] [Created] (IGNITE-2681) Need to add an option to suppress binary marshaller warnings

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-2681:
---

 Summary: Need to add an option to suppress binary marshaller 
warnings
 Key: IGNITE-2681
 URL: https://issues.apache.org/jira/browse/IGNITE-2681
 Project: Ignite
  Issue Type: Improvement
  Components: general
Reporter: Valentin Kulichenko
 Fix For: 1.6


Some users don't want to have warnings like below in the logs, because they are 
printed out for each class and are not always needed. We need to have a way to 
suppress them.

Both quiet mode and logging via {{IgniteLogger}} should be fixed.

{noformat}
[11:37:46] Class "" cannot be serialized using 
BinaryMarshaller because it either implements Externalizable interface or have 
writeObject/readObject methods. OptimizedMarshaller will be used instead and 
class instances will be deserialized on the server. Please ensure that all 
nodes have this class in classpath. To enable binary serialization either 
implement Binarylizable interface or set explicit serializer using 
BinaryTypeConfiguration.setSerializer() method.
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Please review

[Alexey Goncharuk]

Denis,

Changes in IGNITE-2647 look good to me.
​

[jira] [Created] (IGNITE-2680) Terminating running SQL queries

[Denis Magda (JIRA)]

Denis Magda created IGNITE-2680:
---

 Summary: Terminating running SQL queries
 Key: IGNITE-2680
 URL: https://issues.apache.org/jira/browse/IGNITE-2680
 Project: Ignite
  Issue Type: Bug
Reporter: Denis Magda


If to start a long running SQL query over a huge cache will millions of entries 
there should be a way terminate it. Even if {{QueryCursor}} is closed the query 
won't be cancelled consuming available resources.

There should be a way to close a query having using an object that is related 
to it. Seems that ideally we can use {{QueryCursor.close()}} method for that;




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Semaphore blocking on tryAcquire() while holding a cache-lock

[Vladimir Ozerov]

Cross-posting to the dev-list.

Hi Mario,
Thank you for source code. I was able to reproduce the issue and deduced it
to simpler example when two nodes start in a single JVM and one of the
holds key lock. See https://issues.apache.org/jira/browse/IGNITE-2671

Igniters,
I think someone with experience with cache/preload should throw a glance at
this ticket. Looks pretty nasty to me. Essentially, new node cannot join
topology when a single cache key lock is held.

Vladimir.

On Tue, Feb 16, 2016 at 8:33 PM, nyname00  wrote:

> Yakov,
>
> please see the code below. Simply start one node (in my case I started it
> directly from eclipse using 1.8u45) and wait for a few cycles, then start
> up
> the second node. You should see one more "sem created" message and then ...
> silence. If you kill the first node, the code processes normal again - but
> not when you kill the second one.
>
> Also note that on the second node no "Topology snapshot" message appears
> which, I guess, is not a good sign.
>
> I'm still testing, but if you replace the "sched" map-lock with a
> semaphore,
> everything seems to work ... until you kill one of the nodes. Then an
> exception is thrown every time the worker tries to get a new semaphore.
>
> Thanks for investigating,
> Mario
>
>
> public static void main(String[] args) {
> Ignite ignite = Ignition.start(new IgniteConfiguration());
>
> Lock lock = ignite
> .getOrCreateCache(
> new CacheConfiguration Boolean>("sched").setAtomicityMode(TRANSACTIONAL))
> .lock("sched-lock");
>
> if (lock.tryLock()) {
> try {
> System.out.println("pre start sched");
>
> ScheduledExecutorService es =
> Executors.newSingleThreadScheduledExecutor();
> ScheduledFuture f = es.scheduleAtFixedRate(new
> Worker(ignite), 0, 2000,
> TimeUnit.MILLISECONDS);
>
> System.out.println("post start sched");
> try {
> f.get();
> } catch (Exception e) {
> e.printStackTrace();
> } finally {
> es.shutdownNow();
> }
> } finally {
> lock.unlock();
> }
> }
> }
>
> private static class Worker implements Runnable {
> private final Ignite ignite;
>
> public Worker(Ignite ignite) {
> this.ignite = ignite;
> }
>
> @Override
> public void run() {
> IgniteSemaphore sem = ignite.semaphore("sem-worker-1", 1,
> true, true);
>
> System.out.println("sem created");
> if (sem.tryAcquire()) {
> try {
> System.out.println("sem aquired");
> } finally {
> sem.release();
> System.out.println("sem released");
> }
> } else {
> System.out.println("sem not aquired");
> }
> }
> }
>
>
> yakov wrote
> > Hi Mario!
> >
> > Can you please share the code somehow? Reproducible example will be very
> > helpful.
> >
> > --Yakov
> >
> > 2016-02-16 16:57 GMT+03:00 nyname00 
>
> > mario.stark@
>
> > :
> >
> >> Hi Igniters,
> >>
> >> I'm getting some strange behavior when I try to call
> >> IgniteSemaphore#tryAquire() while holding a lock on a cache element -
> the
> >> method seems block forever.
> >>
> >> Here's the details:
> >>   - create a cache (default, transactional) and get a lock using
> >> Lock#tryLock()
> >>   - start a Executors.newSingleThreadScheduledExecutor() and schedule a
> >> worker to run every n seconds
> >>   - in the worker, get a semaphore and call IgniteSemaphore#tryAcquire()
> >>   - do some work and call IgniteSemaphore#release()
> >> (except for the cache/lock and semaphore no Ignite API calls are made)
> >>
> >> The whole thing works for a single node, but as soon as I start up an
> new
> >> node (with the same code) the IgniteSemaphore#tryAcquire() call starts
> >> blocking.
> >>
> >> Is this this a known limitation/issue or am I doing something wrong
> here?
> >>
> >> Thanks in advance,
> >> Mario
> >>
> >> ps: when I replace the cache-lock with an other semaphore, it works
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://apache-ignite-users.70518.x6.nabble.com/Semaphore-blocking-on-tryAcquire-while-holding-a-cache-lock-tp3031.html
> >> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
> >>
>
>
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Semaphore-blocking-on-tryAcquire-while-holding-a-cache-lock-tp3031p3034.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

About issue-1661

[李玉珏]

Hi:

https://issues.apache.org/jira/browse/IGNITE-1661?filter=-2.

The issue is china's developer found, but the community has no feedback.
Today, the issue reporter asked me, but I can't answer.
I would like to ask, does anyone know what the issue is? Are developers 
using incorrect? If it is bug, when can fix it?

[GitHub] ignite pull request: Ignite 2525

[iveselovskiy]

GitHub user iveselovskiy opened a pull request:

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

Ignite 2525



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

$ git pull https://github.com/iveselovskiy/ignite ignite-2525

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

https://github.com/apache/ignite/pull/494.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 #494


commit a652adec401dc11e6f930fcef9de9b2ee5ecdbb9
Author: iveselovskiy 
Date:   2016-02-10T15:54:36Z

added missing file header to 
org.apache.ignite.hadoop.fs.KerberosHadoopFileSystemFactorySelfTest

commit 48f00cac3ba7668247585ab7c257562951c4f04f
Author: iveselovskiy 
Date:   2016-02-11T10:36:12Z

Merge branch 'master' of https://github.com/apache/ignite

commit a5c5ed4d5bbd61c62acfbb19610aac2f710935cd
Author: iveselovskiy 
Date:   2016-02-15T17:58:10Z

Merge branch 'master' of https://github.com/apache/ignite

commit b81ee18308307dad2416f7635120a387b98bb967
Author: iveselovskiy 
Date:   2016-02-17T18:32:53Z

Merge branch 'master' of https://github.com/apache/ignite

commit 7c537a47376f4508af1bba9f23285614fe71ceda
Author: iveselovskiy 
Date:   2016-02-17T18:34:59Z

IGNITE-2525: fixed by adding the tokens to the appSubmissioContext & 
containerLaunchContext.




---
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: About issue 1661

[Denis Magda]

Hi,

Don't hesitate to reaching out community over @dev or @user list if 
there is no feedback in some JIRA ticket.


Alex G., is this issue somehow related to the task you're working on
https://issues.apache.org/jira/browse/IGNITE-2610

On 2/17/2016 4:23 PM, 李玉珏@163 wrote:

Hi:

https://issues.apache.org/jira/browse/IGNITE-1661?filter=-2.

The issue is china's developer found, but the community has no feedback.
Today, the issue reporter asked me, but I can't answer.
I would like to ask, does anyone know what the issue is? Are 
developers using incorrect? If it is bug, when can fix it?

Please review

[Denis Magda]

Igniters,

Please review the critical minor fixes for the following tickets

IGNITE-2647:Cache is undeployed even when BinaryMarshaller is used 



IGNITE-2666: Node is not stopped when RingMessageWorker is interrupted 



In my understanding the review should be done either by Alex G. or Yakov 
or Sam.


--
Denis

Ignite .NET & C++ links on the main website

[Pavel Tupitsyn]

Igniters,

We have released .NET & C++ support in 1.5, but there is not enough
information about these on the main website:

* No mentions in Features
* Documentation submenu is inconsistent across different pages (Download
page does not have .NET links in Documentation submenu for some reason)
* "Ignite for .Net" should be "Ignite.NET"
* API docs and readme.io docs are in different places, which is confusing

Any thoughts on how to improve the situation?

Thanks,

-- 
-- 
Pavel Tupitsyn
GridGain Systems, Inc.
www.gridgain.com

About issue 1661

[李玉珏]

Hi:

https://issues.apache.org/jira/browse/IGNITE-1661?filter=-2.

The issue is china's developer found, but the community has no feedback.
Today, the issue reporter asked me, but I can't answer.
I would like to ask, does anyone know what the issue is? Are developers 
using incorrect? If it is bug, when can fix it?

[GitHub] ignite pull request: Ignite 2649

[dkarachentsev]

GitHub user dkarachentsev opened a pull request:

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

Ignite 2649



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

$ git pull https://github.com/dkarachentsev/ignite ignite-2649

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

https://github.com/apache/ignite/pull/492.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 #492


commit 946dccb9e98419bf9921b12607667d74ef87ecda
Author: dkarachentsev 
Date:   2016-02-10T08:33:04Z

IGNITE-2575 Add limit on minimal value of IGFS IPC port configuration.

commit 3d5999821d0efd6c026adbb3256c86bc798dc1c7
Author: dkarachentsev 
Date:   2016-02-10T08:50:09Z

Merge remote-tracking branch 'upstream/master'

commit 375eb11ba8c9076906971785fdb7bead294d8022
Author: dkarachentsev 
Date:   2016-02-11T09:47:18Z

Merge remote-tracking branch 'upstream/master'

commit 88a11b4554884acd2dbd956fcbd37a8932fbde8e
Author: dkarachentsev 
Date:   2016-02-12T08:39:32Z

Merge remote-tracking branch 'upstream/master'

commit d5f0cc8034fbbe6c34e1061fb7171e9574307413
Author: dkarachentsev 
Date:   2016-02-15T08:24:15Z

IGNITE-2575 Add limit on minimal value of IGFS IPC port configuration. 
Delete method

commit 38a8d6c1d060f5fc120579fe4b348741a30b4a05
Author: dkarachentsev 
Date:   2016-02-15T08:26:58Z

IGNITE-2575 Add limit on minimal value of IGFS IPC port configuration. 
Delete method

commit 7363051446ef571c1c814719b92ee7ce0b4706c4
Author: dkarachentsev 
Date:   2016-02-16T10:02:03Z

Merge remote-tracking branch 'upstream/master'

commit 3523de2a3bdfbb8fcf7a70e3a7be262577d32fce
Author: dkarachentsev 
Date:   2016-02-17T07:35:12Z

Merge remote-tracking branch 'upstream/master'

commit d551fa38acb8a8346dfee62454ee4b74c86fd6da
Author: dkarachentsev 
Date:   2016-02-17T15:45:36Z

IGNITE-2649 - Ignition.localIgnite() unreliable under Gateways and cause 
wrong components deserialization.

commit 60eb7f778f3b4046d9f84908b2fee994edaf37c9
Author: dkarachentsev 
Date:   2016-02-17T15:48:46Z

IGNITE-2649 - Ignition.localIgnite() unreliable under Gateways and cause 
wrong components deserialization. Rollback for example.




---
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: IGNITE-2674: Removed cursor removing in OdbcR...

[isapego]

GitHub user isapego opened a pull request:

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

IGNITE-2674: Removed cursor removing in OdbcRequestHandler.fetchQuery().



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

$ git pull https://github.com/isapego/ignite ignite-2674

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

https://github.com/apache/ignite/pull/491.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 #491






---
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: IGNITE-2156 .Net: add IgniteClientDisconnecte...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2676) Refactor IGFS screen to Angular directives

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-2676:


 Summary: Refactor IGFS screen to Angular directives
 Key: IGNITE-2676
 URL: https://issues.apache.org/jira/browse/IGNITE-2676
 Project: Ignite
  Issue Type: Sub-task
  Components: wizards
Affects Versions: 1.5.0.final
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2675) ODBC: Query ID is insecure.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2675:
---

 Summary: ODBC: Query ID is insecure.
 Key: IGNITE-2675
 URL: https://issues.apache.org/jira/browse/IGNITE-2675
 Project: Ignite
  Issue Type: Sub-task
  Components: odbc
Affects Versions: 1.5.0.final
Reporter: Vladimir Ozerov
Assignee: Igor Sapego
Priority: Critical
 Fix For: 1.6


Query cursor ID is created using AtomicLong. It means that malicious user could 
easily read data from any other cursor by simply bruteforcing identifiers.

To fix that query ID must be a composite of current session ID and unique 
identifier.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2674) Cursors should be removed in case of exception only in OdbcRequestHandler.executeQuery() method.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2674:
---

 Summary: Cursors should be removed in case of exception only in 
OdbcRequestHandler.executeQuery() method.
 Key: IGNITE-2674
 URL: https://issues.apache.org/jira/browse/IGNITE-2674
 Project: Ignite
  Issue Type: Sub-task
Reporter: Vladimir Ozerov
Assignee: Igor Sapego


It is not clear why do we remove query cursor from map in case of exception in 
OdbcRequestHandler.fetchQuery(). 

If user has some try-finally construct on the client side and will try to close 
the request after this exception, he will receive another one from close() 
method.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-2673) ODBC: Potential memory leak when Throwable is thrown inside OdbcRequestHandler

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2673:
---

 Summary: ODBC: Potential memory leak when Throwable is thrown 
inside OdbcRequestHandler
 Key: IGNITE-2673
 URL: https://issues.apache.org/jira/browse/IGNITE-2673
 Project: Ignite
  Issue Type: Sub-task
  Components: odbc
Affects Versions: 1.5.0.final
Reporter: Vladimir Ozerov
Assignee: Igor Sapego
Priority: Critical
 Fix For: 1.6


Some methods in OdbcRequestHandler follow the same pattern:
{code}
try {
...
}
catch (Exception e) {
qryCurs.remove(req.queryId());
}
{code}

Should Error be thrown there, qryCurs will never be cleared.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request: IGNITE-2627: Removed OdbcNioParser. Using Gri...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2672) ignite-benchmarks.jar should not be included into build.

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-2672:
---

 Summary: ignite-benchmarks.jar should not be included into build.
 Key: IGNITE-2672
 URL: https://issues.apache.org/jira/browse/IGNITE-2672
 Project: Ignite
  Issue Type: Bug
  Components: build
Affects Versions: 1.5.0.final
Reporter: Vladimir Ozerov
Assignee: Anton Vinogradov
Priority: Critical
 Fix For: 1.6


This project is for intenrnal testing only, so no need to include it into 
resulting binaries.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)