I responded to this question here:
http://stackoverflow.com/questions/39646507/apache-ignite-thread-gets-blocked-forever/39671453
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-Thread-gets-blocked-forever-tp7883p7936.html
Sent from the Apache
Hi Alex,
I ran your example and now understand what you were talking about. I don't
think there is an easy way to solve this. I think you should load the data
using loadCache method making sure that this is done on consistent topology
which should be the same as when the cluster was stopped.
-Val
Hi,
Expiration comes from JCache API, while evictions are added by Ignite. And
actually I think it's correct that these are different APIs, because
features are different.
As for the custom expiration, you can try to implement your own
ExpiryPolicy.
-Val
--
View this message in context:
http
Hi,
Are other clients able to connect? Can you attach full logs?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignitevisorcmd-can-not-connect-to-the-cluster-tp7692p7933.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
I would advise against using the initial query for building a consistent view
because of the way the feature is currently implemented in Ignite. The current
API makes it impossible to establish the ordering relationship between the
events delivered via the CQ listener and the data items returned
Hi Guang,
You can specify your custom IgniteBiPredicate implementation if you need
some custom pre-processing for each key-value pair loaded from persistent
store.
Yes you can pass more that one query using something like that:
cache3.loadCache(null, "select * from my_table_1", "select * from m
Hi,
Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages. To subscribe, send empty
email to user-subscr...@ignite.apache.org and follow simple instructions in
the reply.
its_panwar wrote
> I have a cluster of 2 nodes (A & B).
>
>
Cool, it worked!
Since I am newbie, would you mind to explain the two input parameters for
loadCache method? Based on the warning (below) raised in Eclipse for this
line of code, I can see the first parameter is IgniteBiPredicate type. How
should this parameter be used? Can I pass more than one qu
It will enable by default if ignite-log4j module is added to classpath. I
would check that this is actually the case first, probably you missed
something and it was not properly added.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Logging-failing-tried-th
Hi,
Please properly subscribe to the mailing list so that the community can
receive email notifications for your messages. To subscribe, send empty
email to user-subscr...@ignite.apache.org and follow simple instructions in
the reply.
junyoung.kang wrote
> I have two question.
>
> First, This i
Hi Alper,
No, this is not possible to know the mapping without connecting to the
cluster, because affinity depends on topology. Good approach for such cases
is using the REST API [1], but current implementation is limited though. So
you will probably have to create your own endpoint and run it as
Bob,
See my response here:
http://apache-ignite-users.70518.x6.nabble.com/A-very-slow-code-of-using-entryprocessor-why-td7902.html
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/How-to-get-all-keys-of-cache-most-quickly-tp7899p7924.html
Sent from the Apac
Hi Bob,
Each invoke is a synchronous network operation, so it's speed depends mostly
on network latency. However, it looks like you're processing the whole data
set. In this I would recommend to broadcast a closure using Compute Grid [1]
and within the closure iterate through the local data using
Hi,
You can use ContinuousQuery.setInitialQuery to get the state of the cache at
the moment of query execution. The results for this query will be returned
in the cursor returned from the query() method. Note that in this case
listener is actually registered before the initial query execution, so
Hi Satoshi,
I can't reproduce this. How do you check the size of the near cache?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Question-about-rmvall-command-of-Rest-API-tp7903p7921.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com
Hi,
I don't this it's Ignite related. Can you show the full log?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Fatal-Error-42-19-The-element-type-p-must-be-terminated-by-the-matching-end-tag-p-tp7911p7920.html
Sent from the Apache Ignite Users mailing li
Hi Guang,
Try this:
*cache3.loadCache(null, new String[] {"select * from test1.pojo_test3 limit
10"});*
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Cannot-query-on-a-cache-using-Cassandra-as-a-persistent-store-tp7870p7918.html
Sent from the Apache Ignite
Hi Val,
You are right! There is no @QuerySqlField on any of the fields in Person
class.
After adding this annotation to the getter of Age field, I was able to query
on the Age field.
/** */
@SuppressWarnings("UnusedDeclaration")
*@QuerySqlField (name = "age", index = true)*
publ
Oh really...so you were able to get responses back once you hit the odata
end point? Did you try this running on IIS or IIS Express?
On Fri, Sep 23, 2016 at 1:10 PM, Pavel Tupitsyn
wrote:
> I've tried your code and it works for me.
> The only issue I see is that you start Ignite client on each w
I've tried your code and it works for me.
The only issue I see is that you start Ignite client on each web request,
so the second request fails with "Default Ignite instance has already been
started".
Suggestions:
* Examine Windows Application Log for some clues
* Try IIS instead of IIS Express
I am getting this error on Ignite Startup. It does not seem to effect
anything as caching seems to be working as desired. I see no xml syntax
errors in my configuration files. Do we know what is causing this? Using
version 1.7
[Fatal Error] :42:19: The element type "p" must be terminated by the
ma
Hi,
I almost certain, which the issue in access right.
You can check it write simple java code which modify the file and run under
same the system user.
On Fri, Sep 23, 2016 at 1:47 PM, chevy wrote:
> Any workaround for this issue?
>
>
>
> --
> View this message in context: http://apache-ignite
I was using the sample Odata project available on internet and updated that
to test with Ignite. There are 2 projects.
ODataMusicServer - .Net console app that populates cache
https://github.com/ksatya77/ODataMusicServer
ODataMovies - ASP.NET Odata API that tries to access the cache as a client:
Can you attach an entire project so I take a look?
On Fri, Sep 23, 2016 at 3:59 PM, Murthy Kakarlamudi
wrote:
> Hi Pavel,
>No it does not give any exception. Just get an error saying that the
> Site can't be reached when I invoke the OData endpoint. Below is the
> console ouput. iisexpress.e
Hi Pavel,
No it does not give any exception. Just get an error saying that the
Site can't be reached when I invoke the OData endpoint. Below is the
console ouput. iisexpress.exe just exits without any error code.
As Server class is not resolved, I had to make a slight modification as
below:
var
Any workaround for this issue?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Failed-to-write-class-name-to-file-java-io-FileNotFoundException-tp7855p7906.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
class org.apache.ignite.IgniteException: null
at
org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:908)
at
org.apache.ignite.internal.processors.datastructures.GridCacheAtomicSequenceImpl.incrementAndGet(GridCacheAtomicSequenceImpl.java:178)
at
ig
Following is my test steps about continuous query.
step 1: Start an Ignite Server by command "sh ignite.sh".
step 2: Start an Ignite Client, it will do continuous query for cache1.
The main code is as follows
Ignition.setClientMode(true);
Ignite ignite = Ignition.start();
Hi,
When the bellow rmvall command of Rest API was executed, cache entries of
servers have removed, but near cache entries of clients have NOT removed.
Is this a bug?
$ curl 'localhost:8080/ignite?cmd=rmvall&cacheName=xxx'
Could you tell me the way to clear all cache using Rest API if such way
e
hi, everyone
The code and related log are the following content, how can I do to
increase the performance? Thank you very much.
Code:
IgniteCache>> mapMatchingData =
IgniteManager.getInstance().getMapMatchingData();
Iterator>>> it1 =
mapMatchingData.iterator();
while(it1.hasNext(
Hi,
1) The code looks good to me. What exactly is the issue? Is there an
exception, or do you get incorrect results?
2) There is a known issue with IIS: it performs a shadow-copy [1] of
application assemblies (dll files), which makes it impossible for Ignite to
detect Libs directory with jar files
Hi Val.
We use ignite as client in our GUI app that mostly used by our
clients. When our servers are on amazon it is imposibble to connet
servers because most of the time it is impossible to configure port
forwarding on the router.
Other than that we have issues on waiting time for clients to con
Hi, everyone,
About this question, I search the mail list and Ignite java doc, but no
suitable answer was found.
My use case is, I have a cache whose structure is IgniteCache>>.
I want loop all entries to remove some entries in Map value.
So, first, I want to get all keys, and
33 matches
Mail list logo
