Re: index and query org.apache.ignite.spark.IgniteRDD[String,org.apache.spark.sql.Row]

[vkulichenko]

P.S. Here is the ticket for keepBinary flag in IgniteRDD:
https://issues.apache.org/jira/browse/IGNITE-2821



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/index-and-query-org-apache-ignite-spark-IgniteRDD-String-org-apache-spark-sql-Row-tp3343p3467.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

DataStreamers and Daemon-mode

[Colin Waters]

Hi all,

In Ignite 1.3.0-incubating I was able to populate a cache on my grid with
data via a DataStreamer running in Daemon-mode. From Ignite 1.4 I get a
"Cache doesn't exist".

I'm not sure if this is a issue with my approach to data-loading and is
therefore a deliberate feature change? My approach so far has been to
start-up a number of "data-nodes", then run the data-load via a separate
Java process. I'm happy to take pointers on a better way.

I've reproduced the issue in fairly cutdown example code and you can see it
at https://github.com/waters-colin/ignite-dataloading
You can observe the different behaviour by changing the $IGNITE_HOME as
well as the ignite dependency version in the pom.

The Stack I get on error is:

Exception in thread "main" java.lang.IllegalStateException: Cache doesn't
exist: city-cache
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.cacheConfiguration(GridCacheProcessor.java:3051)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.(DataStreamerImpl.java:240)
at
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.dataStreamer(DataStreamProcessor.java:171)
at
org.apache.ignite.internal.IgniteKernal.dataStreamer(IgniteKernal.java:2756)
at ignite.example.CityBulkLoader.loadAll(CityBulkLoader.java:28)
at ignite.example.DataLoadingApp.loadData(DataLoadingApp.java:45)
at ignite.example.DataLoadingApp.main(DataLoadingApp.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)

I can see that there was a check for isDaemon() added to
GridCacheProcessor.start() CacheConfiguration loop ~ line 601 and that when
this check is commented that I again can use the DataStreamer ok. Is it
expected to be able to use an IgniteDataStreamer from code running with
Ignition.setDaemon(true)?

All the best,
Colin.

Re: Connecting Amazon cluster with client from local

[vkulichenko]

Hi Alper,

That's a tricky question :)

This is possible to achieve if you implement AddressResolver that will map
private address to public address and provide it in the configuration
(IgniteConfiguration.setAddressResolver). This will add public address to
node attributes, and client node will know how to connect. On Amazon you can
use the special metadata URL [1] to get the public address. See [2] for more
details.

[1] http://169.254.169.254/latest/meta-data/public-ipv4
[2]
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-instance-addressing.html

In addition Ignite currently requires bi-directional connection even between
client and server, i.e. server has to be able to establish TCP connection
with client. This means that if your client is behind NAT (which is often
the case), you will have to provide proper address resolver there as well,
and configure port forwarding on the router.

This is something that should be seriously improved from usability
standpoint, I will create a ticket.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Connecting-Amazon-cluster-with-client-from-local-tp3453p3464.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: websession clustering problem

[vkulichenko]

Slavo,

Looks like you used an instance of void.class as one of the attributes.
There is a bug in current version which causes the failure in this case. Can
you check if that's what really happened?

I also just committed the fix. So if you build Ignite from master, it should
work for you.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/websession-clustering-problem-tp3437p3463.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Client configuration - help

[vkulichenko]

Hi Arthi,

Can you please show the whole trace?

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Client-configuration-help-tp3454p3462.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Hibernate connection inspite of jdbc?

[vkulichenko]

Hi,

It looks like your Hibernate configuration file is broken (most likely has
invalid XML). Did you modify the one provided in the example?

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Hibernate-connection-inspite-of-jdbc-tp3412p3460.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: org.apache.ignite.IgniteCheckedException: Failed to register query type: TypeDescriptor

[vkulichenko]

Hi,

Can you please properly subscribe to the mailing list so that community
receives email notifications? Follow the instruction here:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1


navy wrote
> After I load the data from mysql,I try to read it with sqlQuery,but When I
> put the jar ignite-indexing to my project,some error will
> happen.org.apache.ignite.IgniteCheckedException: Failed to register query
> type: TypeDescriptor,Caused by: org.h2.jdbc.JdbcSQLException: Column
> "CARD_NO" not found; SQL statement.

Can you show your test code, model classes and cache configuration?

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/org-apache-ignite-IgniteCheckedException-Failed-to-register-query-type-TypeDescriptor-tp3447p3459.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

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

[Dmitriy Setrakyan]

On Fri, Mar 11, 2016 at 10:20 AM, Christos Erotocritou <
chris...@gridgain.com> wrote:

> We already have a basic FAQ page which I am populating:
> http://apacheignite.gridgain.org/docs/faq <
> http://apacheignite.gridgain.org/docs/faq>
>
> Please feel free to add to it.
>

Thanks Christos! Here is the correct link (your link is just an alias):
https://apacheignite.readme.io/docs/faq

I think we should add a TOC up top as well, whenever you are done.


> Not sure if we want to migrate this to the wiki?
>

I don’t think we need to.


>
> Christos
>
> > On 11 Mar 2016, at 17:35, Dmitriy Setrakyan 
> wrote:
> >
> > +1 on FAQ
> >
> > Can we just create a page, and start populating it?
> >
> > D.
> >
> > On Fri, Mar 11, 2016 at 3:25 AM, Anton Vinogradov <
> avinogra...@gridgain.com>
> > wrote:
> >
> >> Yakov,
> >>
> >> I've answered.
> >> Seems we have to have special FAQ section at Ignite wiki to publish same
> >> things.
> >>
> >> On Sun, Mar 6, 2016 at 12:21 PM, Yakov Zhdanov 
> >> wrote:
> >>
> >>> Vlad and all (esp Val and Anton V.),
> >>>
> >>> I reviewed the PR. My comments are in the ticket.
> >>>
> >>> Anton V. there is a question regarding optimized-classnames.properties.
> >>> Can you please respond in ticket?
> >>>
> >>>
> >>> --Yakov
> >>>
> >>> 2016-02-29 16:00 GMT+06:00 Yakov Zhdanov :
> >>>
>  Vlad, that's great! I will take a look this week. Reassigning ticket
> to
>  myself.
> 
>  --Yakov
> 
>  2016-02-26 18:37 GMT+03:00 Vladisav Jelisavcic :
> 
> > Hi,
> >
> > i recently implemented distributed ReentrantLock - IGNITE-642,
> > i made a pull request, so hopefully this could be added to the next
> > release.
> >
> > Best regards,
> > Vladisav
> >
> > On Thu, Feb 18, 2016 at 10:49 AM, Alexey Goncharuk <
> > alexey.goncha...@gmail.com> wrote:
> >
> >> Folks,
> >>
> >> The current implementation of IgniteCache.lock(key).lock() has the
> > same
> >> semantics as the transactional locks - cache topology cannot be
> > changed
> >> while there exists an ongoing transaction or an explicit lock is
> > held. The
> >> restriction for transactions is quite fundamental, the lock() issue
> > can be
> >> fixed if we re-implement locking the same way IgniteSemaphore
> > currently
> >> works.
> >>
> >> As for the "Failed to find semaphore with the given name" message,
> my
> > first
> >> guess is that DataStructures were configured with 1 backups which
> led
> > to
> >> the data loss when two nodes were stopped. Mario, can you please
> > re-test
> >> your semaphore scenario with 2 backups configured for data
> structures?
> >> From my side, I can also take a look at the semaphore issue when I'm
> > done
> >> with IGNITE-2610.
> >>
> >
> 
> 
> >>>
> >>
>
>

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

[Christos Erotocritou]

Ah, I realise now that this FAQ you are talking about is probably more of a dev 
one where as the one I’ve created is more product focused.

Christos 

> On 11 Mar 2016, at 18:20, Christos Erotocritou  wrote:
> 
> We already have a basic FAQ page which I am populating:
> http://apacheignite.gridgain.org/docs/faq 
> 
> 
> Please feel free to add to it.
> 
> Not sure if we want to migrate this to the wiki?
> 
> Christos
> 
>> On 11 Mar 2016, at 17:35, Dmitriy Setrakyan > > wrote:
>> 
>> +1 on FAQ
>> 
>> Can we just create a page, and start populating it?
>> 
>> D.
>> 
>> On Fri, Mar 11, 2016 at 3:25 AM, Anton Vinogradov > >
>> wrote:
>> 
>>> Yakov,
>>> 
>>> I've answered.
>>> Seems we have to have special FAQ section at Ignite wiki to publish same
>>> things.
>>> 
>>> On Sun, Mar 6, 2016 at 12:21 PM, Yakov Zhdanov >> >
>>> wrote:
>>> 
 Vlad and all (esp Val and Anton V.),
 
 I reviewed the PR. My comments are in the ticket.
 
 Anton V. there is a question regarding optimized-classnames.properties.
 Can you please respond in ticket?
 
 
 --Yakov
 
 2016-02-29 16:00 GMT+06:00 Yakov Zhdanov >:
 
> Vlad, that's great! I will take a look this week. Reassigning ticket to
> myself.
> 
> --Yakov
> 
> 2016-02-26 18:37 GMT+03:00 Vladisav Jelisavcic  >:
> 
>> Hi,
>> 
>> i recently implemented distributed ReentrantLock - IGNITE-642,
>> i made a pull request, so hopefully this could be added to the next
>> release.
>> 
>> Best regards,
>> Vladisav
>> 
>> On Thu, Feb 18, 2016 at 10:49 AM, Alexey Goncharuk <
>> alexey.goncha...@gmail.com > wrote:
>> 
>>> Folks,
>>> 
>>> The current implementation of IgniteCache.lock(key).lock() has the
>> same
>>> semantics as the transactional locks - cache topology cannot be
>> changed
>>> while there exists an ongoing transaction or an explicit lock is
>> held. The
>>> restriction for transactions is quite fundamental, the lock() issue
>> can be
>>> fixed if we re-implement locking the same way IgniteSemaphore
>> currently
>>> works.
>>> 
>>> As for the "Failed to find semaphore with the given name" message, my
>> first
>>> guess is that DataStructures were configured with 1 backups which led
>> to
>>> the data loss when two nodes were stopped. Mario, can you please
>> re-test
>>> your semaphore scenario with 2 backups configured for data structures?
>>> From my side, I can also take a look at the semaphore issue when I'm
>> done
>>> with IGNITE-2610.
>>> 
>> 
> 
> 
 
>>> 
> 

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

[Dmitriy Setrakyan]

+1 on FAQ

Can we just create a page, and start populating it?

D.

On Fri, Mar 11, 2016 at 3:25 AM, Anton Vinogradov 
wrote:

> Yakov,
>
> I've answered.
> Seems we have to have special FAQ section at Ignite wiki to publish same
> things.
>
> On Sun, Mar 6, 2016 at 12:21 PM, Yakov Zhdanov 
> wrote:
>
>> Vlad and all (esp Val and Anton V.),
>>
>> I reviewed the PR. My comments are in the ticket.
>>
>> Anton V. there is a question regarding optimized-classnames.properties.
>> Can you please respond in ticket?
>>
>>
>> --Yakov
>>
>> 2016-02-29 16:00 GMT+06:00 Yakov Zhdanov :
>>
>>> Vlad, that's great! I will take a look this week. Reassigning ticket to
>>> myself.
>>>
>>> --Yakov
>>>
>>> 2016-02-26 18:37 GMT+03:00 Vladisav Jelisavcic :
>>>
 Hi,

 i recently implemented distributed ReentrantLock - IGNITE-642,
 i made a pull request, so hopefully this could be added to the next
 release.

 Best regards,
 Vladisav

 On Thu, Feb 18, 2016 at 10:49 AM, Alexey Goncharuk <
 alexey.goncha...@gmail.com> wrote:

 > Folks,
 >
 > The current implementation of IgniteCache.lock(key).lock() has the
 same
 > semantics as the transactional locks - cache topology cannot be
 changed
 > while there exists an ongoing transaction or an explicit lock is
 held. The
 > restriction for transactions is quite fundamental, the lock() issue
 can be
 > fixed if we re-implement locking the same way IgniteSemaphore
 currently
 > works.
 >
 > As for the "Failed to find semaphore with the given name" message, my
 first
 > guess is that DataStructures were configured with 1 backups which led
 to
 > the data loss when two nodes were stopped. Mario, can you please
 re-test
 > your semaphore scenario with 2 backups configured for data structures?
 > From my side, I can also take a look at the semaphore issue when I'm
 done
 > with IGNITE-2610.
 >

>>>
>>>
>>
>

Connecting Amazon cluster with client from local

[Alper Tekinalp]

Hi all.

Is there a way to connect an amazon cluster from local client?

I tried to use static ip discovery with public ip of node. It seems to
find the cluster but cant connect. As I understand from error
messages, client tries to use internal ip of server node for other
things.

How can I workaround that? Is there a suitable way to implement?



-- 
Alper Tekinalp

Software Developer

Evam Stream Analytics

Atatürk Mah.Turgut Özal Bulvarı Gardenya 1 Plaza 42/B K:4 Ataşehir / İSTANBUL

Tlf : +90216 688 45 46 Fax : +90216 688 45 47 Gsm:+90 536 222 76 01

www.evam.com

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

[Anton Vinogradov]

Yakov,

I've answered.
Seems we have to have special FAQ section at Ignite wiki to publish same
things.

On Sun, Mar 6, 2016 at 12:21 PM, Yakov Zhdanov  wrote:

> Vlad and all (esp Val and Anton V.),
>
> I reviewed the PR. My comments are in the ticket.
>
> Anton V. there is a question regarding optimized-classnames.properties.
> Can you please respond in ticket?
>
>
> --Yakov
>
> 2016-02-29 16:00 GMT+06:00 Yakov Zhdanov :
>
>> Vlad, that's great! I will take a look this week. Reassigning ticket to
>> myself.
>>
>> --Yakov
>>
>> 2016-02-26 18:37 GMT+03:00 Vladisav Jelisavcic :
>>
>>> Hi,
>>>
>>> i recently implemented distributed ReentrantLock - IGNITE-642,
>>> i made a pull request, so hopefully this could be added to the next
>>> release.
>>>
>>> Best regards,
>>> Vladisav
>>>
>>> On Thu, Feb 18, 2016 at 10:49 AM, Alexey Goncharuk <
>>> alexey.goncha...@gmail.com> wrote:
>>>
>>> > Folks,
>>> >
>>> > The current implementation of IgniteCache.lock(key).lock() has the same
>>> > semantics as the transactional locks - cache topology cannot be changed
>>> > while there exists an ongoing transaction or an explicit lock is held.
>>> The
>>> > restriction for transactions is quite fundamental, the lock() issue
>>> can be
>>> > fixed if we re-implement locking the same way IgniteSemaphore currently
>>> > works.
>>> >
>>> > As for the "Failed to find semaphore with the given name" message, my
>>> first
>>> > guess is that DataStructures were configured with 1 backups which led
>>> to
>>> > the data loss when two nodes were stopped. Mario, can you please
>>> re-test
>>> > your semaphore scenario with 2 backups configured for data structures?
>>> > From my side, I can also take a look at the semaphore issue when I'm
>>> done
>>> > with IGNITE-2610.
>>> >
>>>
>>
>>
>