Hi,
the following log message:
[2020-05-12T18:17:57,071][INFO ][main][GridCacheProcessor] Started cache
in recovery mode [name=CO_CO_LINE_NEW, id=1742991829,
dataRegionName=default, mode=PARTITIONED, atomicity=ATOMIC, backups=1,
mvcc=false]
I have the following questions:
1.What has been
Hi,
I have a 3 node ignite cluster which stores data in SQL tables. All the
tables and table contents can be seen with sqline.sh tool.
How can I export these tables as an SQL DB file for future reference?
Cheers,
NSquare
Hi community,
I know that during the startup process of ignite node, cached data will
not be loaded, that is, there is no warm up process.
However, we can see from the top command that during the startup of
ignite, the memory usage has been increasing, which will increase by
more than 10g,
Hi James,
This is a very good catch!
I've filed a ticket, we'll fix it in the next version:
https://issues.apache.org/jira/browse/IGNITE-13031
For now please continue using SqlQuery, it is functional as before.
Thank you,
Pavel
On Tue, May 19, 2020 at 10:42 AM Barney Pippin <
Hello!
It is possible that Data Streamer is not actually aware of affinity column
of your table. Can you try marking it with @AffinityKeyMapped?
Regards,
--
Ilya Kasnacheev
вт, 19 мая 2020 г. в 01:48, narges saleh :
> It seems the issue exist only if one uses data streamer with binaryobject
Which thin client are you referring to?
Best Regards,
Igor
On Mon, May 18, 2020 at 5:09 PM scriptnull
wrote:
> I would like to break down this question into two questions.
>
> 1. Can we have key-values with different expire times in the same cache? (I
> think the answer for this is yes,
Hello, I have 4 remote node for server mode.
I'd like to monitoring that nodes using JMX.
I want to get CPU, THREAD, HEAP, OFFHEAP, GC and so on..
Can I get thoes things( CPU, THREAD, Heap, offheap, gc) each node??
I figured out there are MXBean(CacheMetrics, CacheGroup, DataRegion,
Hi,
I'm just upgrading to Ignite 2.8 and see that SqlQuery has been deprecated
directing us to SqlFieldsQuery, ScanQuery or Text. Previously I had a
continuous query running that took an SqlQuery which had "order by xyz" as
part of the initial query so I could get ordered results back upfront.
Can you please describe the use case in more detail?
What do you expect from such a feature?
On Tue, May 19, 2020 at 2:01 AM martybjo...@gmail.com
wrote:
> I wanted to see if there are any plans to support near caches for thin
> clients? I think it would be a great feature. I know I could use
Hello!
See below inline:
пт, 15 мая 2020 г. в 23:59, nithin91 <
nithinbharadwaj.govindar...@franklintempleton.com>:
> Hi
>
> Although this seems to be working.
> I have following queries with this approach.Can you please
> provide your inputs/suggestions.
>
>
>
> We are
The use case is having a local cache that stores most widely used cache
items in memory on server instead of having the network expense of pulling
them down every time they are requested. The main thing is the near cache
has to support removing cache items that have expired on the server.
The
Hi,
Yes, every cache request has Flags byte right after cacheId.
There is FLAG_WITH_EXPIRY_POLICY = 0x04.
When this flag is set, server expects 3 long values (3x8 bytes) after flags
byte,
representing TTL for Create, Update, and Access, in milliseconds
For example, if we want to store a cache
Hi,
I am referring to any of the thin clients (java/.net/c++/node.js/python/php)
documented at https://apacheignite.readme.io/docs/thin-clients
I wonder if any of those thin clients have an API to set TTL for a key-value
in a cache. If so I can reverse engineer the implementation of it and
Ok, thanks for the explanation.
Yes, this is a good feature, and I've had this in mind for some time.
Ticket filed: https://issues.apache.org/jira/browse/IGNITE-13037
There are no immediate plans, but I think there is a possibility to achieve
this by the end of the year.
On Tue, May 19, 2020 at
Awesome, that's exactly the information that I needed. So we will have to set
the flag byte while doing OP_CACHE_PUT.
Do you know by any chance if there is support for setting expire times for
multiple key-values while doing a OP_CACHE_PUT_ALL (opcode: 1004) operation?
I am guessing the answer is
> if there is support for setting expire times for multiple key-values
> while doing a OP_CACHE_PUT_ALL
The answer is yes. All key-val operations support expiration, namely:
OP_CACHE_PUT
OP_CACHE_PUT_IF_ABSENT
OP_CACHE_PUT_ALL
OP_CACHE_GET_AND_PUT
OP_CACHE_GET_AND_REPLACE
> you could specify the expiration policy on the actual "Put" call itself
That is true on the protocol level.
User-facing API has WithExpiryPolicy so we don't have to add an additional
overload for every cache operation.
On Tue, May 19, 2020 at 5:00 PM Marty Jones wrote:
> Pavel,
>
> My bad, I
Marty, can you please elaborate?
We are talking about protocol-level details in this thread.
Your code for .NET Thin Client seems to be fine, does it work as expected?
On Tue, May 19, 2020 at 4:39 PM Marty Jones wrote:
> I am not seeing that option in the ASP.NET thin client. This is how I
>
I am not seeing that option in the ASP.NET thin client. This is how I
accomplished setting an expiration policy:
ICacheClient cache = igniteClient.GetCache("testCache");
cache.WithExpiryPolicy(new ExpiryPolicy(TimeSpan.FromSeconds(15), null,
null))
.Put("test1", new CacheItemEntry() {
Pavel,
My bad, I misunderstood the question. The code I am using works fine. I
thought the previous discussion was stating that you could specify the
expiration policy on the actual "Put" call itself.
On Tue, May 19, 2020 at 8:53 AM Pavel Tupitsyn wrote:
> Marty, can you please elaborate?
>
Hi,
You can record data output from sqlline
0: jdbc:ignite:thin://127.0.0.1/> !outputformat csv
jdbc:ignite:thin://127.0.0.1/> !record data.csv
Saving all output to "data.csv". Enter "record" with no arguments to stop
it.
0: jdbc:ignite:thin://127.0.0.1/> select * from Person
here
It looks like the Visor CLI can only operate on existing caches, not create
new ones. Is that correct?
Hi,
Some node information, like CPU & heap memory, can be found in
ClusterLocalNodeMetricsMXBeanImpl.
As per memory metrics - they are described here:
https://apacheignite.readme.io/docs/memory-metrics#getting-metrics
Evgenii
вт, 19 мая 2020 г. в 01:52, kay :
> Hello, I have 4 remote node for
Hi
Thanks For the inputs.
To the question is this way of refreshing the cache is efficient, i mean
refreshing the cache using the following process.
We have created a REST-API using Spring Boot which refreshes a particular
cache when a GET Request is triggered.
*Sample REST-API Url :*
Hi
Thanks for the inputs.
I have few queries.
For example i have few caches which have custom key a JAVA POJO Class and
custom Value which is also a JAVA POJO Class.Currently i am unable to do
Cache.invoke and Cache.invokeall operations with peer class loading(i.e
facing class Not Found
Hi,
If you've enabled persistence then some data will be loaded.
Use metrics to see what/how much was loaded:
see: https://apacheignite.readme.io/docs/distributed-persistent-store
https://apacheignite.readme.io/docs/durable-memory#persistence-features
I always get these two warnings. Persistence is on.
Warning 1:
```
[WARNING][checkpoint-runner-#569][GridCacheDatabaseSharedManager] 3
checkpoint pages were not written yet due to unsuccessful page write lock
acquisition and will be retried
yes. That is correct:
https://apacheignite-tools.readme.io/docs/command-line-interface
use the "help cache" command inside the visor to see all of the
capabilities.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Like it says, these are warnings.
Warning 1: This means that a lock couldn't be acquired when starting a
check-pointing operation.
This operation will be re-tried. see:
https://apacheignite.readme.io/docs/persistence-checkpointing
Warning 2: This means that the continuous query
How do you guys handle invalidating cache items when the underlying data is
changed within say a database you are using to create cache items with?
My query is
SELECT * FROM URLS WHERE APPNAME_ID = ? ORDER BY SCORE LIMIT ?
That is giving me 0.7-1.0 msec read performance for a test run for about
some time. But the index with URLS (SCORE ASC, APPNAME_ID), I'm getting a
read performance of about 0.3 to 0.5 msec. i found it to be constant when
31 matches
Mail list logo
