Hi,
attached a small scala project. Just set the build path to src after
building and compiling with sbt.
We want to execute processes that happen outside the JVM. These processes
can be extremely memory intensive which is why I am limiting the
number of parallel jobs that can be executed on a
Hi,
Execute the following statement:
ALTER USER ignite WITH PASSWORD 'test123';
The error message is as follows:
SQL 错误 [1] [5]: Operation failed
[nodeId=88b03674-04a4-44cb-bd42-8f2ed1e980ff,
opId=5b656f9fc61-7cd6fa68-ee67-49d4-aee8-60958f5584af, err=class
please send an email to user-unsubscr...@ignite.apache.org
在 2019/9/4 上午9:44, Jason Man, CLSA 写道:
Please unsubscribe
Thanks.
The content of this communication is intended for the recipient and is
subject to CLSA Legal and Regulatory Notices.
These can be viewed at
Please unsubscribe
Thanks.
The content of this communication is intended for the recipient and is subject
to CLSA Legal and Regulatory Notices.
These can be viewed at https://www.clsa.com/disclaimer.html or sent to you upon
request.
Please consider before printing. CLSA is ISO14001 certified
Hello Uwe,
Why don't you create separate cache corresponding to each table in rdbms?
Best Regards,
Gaurav
On Tue, Sep 3, 2019, 8:31 PM Uwe Geercken wrote:
>
> Hello,
>
> my first post here for Apache Ignite...
>
> I have a question and looking for some advice. I have data from a
> relational
Hello,
my first post here for Apache Ignite...
I have a question and looking for some advice. I have data from a relational database which I will load into Ignite. Each table from the source system has a UID (number), to uniquely identify each record.
If I understand it correctly,
On latest version of apache.ignite. Installed as Windows service on Win 2016.
Added this entry to AppSettings section in Apache.Ignite.exe.config:
If I launch apache.ignite.exe via command prompt, it reads the above config
correctly. If I launch from the same location as service, the config
Hi,
By default Ignite will handle only updates that were done using Ignite
cache API.
I guess that you have already read next article:
https://www.gridgain.com/resources/blog/apache-ignite-transactions-architecture-transaction-handling-level-3rd-party
BR,
Andrei
9/3/2019 2:03 PM, bijunathg
Hi,
Some remarks about job stealing SPI:
1)You have some nodes that can proceed the tasks of some compute job.
2)Tasks will be executed in public thread pool by default:
https://apacheignite.readme.io/docs/thread-pools#section-public-pool
3)If some node thread pool is busy then some task of
Actually, I looked closer at my code. Cannot use getAll() and the Queue is
single partition, so can't use multiple threads, the application is per
event and we have tested it up to 3K events per second not including the
cache.
But also the application a fully async using vertx.io. Looking closer
Thanks - that does seem to be effective at stopping the OOM condition at
least.
Is there any way to determine which cache entries were affected by the page
expiry, do you know? The EVT_CACHE_ENTRY_EVICTED doesn't seem to get fired
in this case as far as I can tell. Is that your expectation?
This
Hi,
We have strict transactional requirements to query and update some cached
data. Our queries are mostly SQL and so we fully load data at application
startup. Our cached data is huge so we use a partitioned cache for
scalability.
Also for some BI applications, we need to write the data into an
Hi,
Our application wants to do SQL queries and writes on some cached data
(partitioned) and at the same time update some other non-cached data in the
same transactional context. We do not want to cache everything for
optimizing the cache memory footprint.
The data-store could be any RDBMS store.
Hi Vlad,
I see that the problem is solved, but do you have the full error message?
Thanks,
Pavel
On Tue, Sep 3, 2019 at 8:04 AM vladtovbin wrote:
> Installing 2010 MFC redistributable actually fixed the issue. Thought it
> was
> not needed in the latest version, but I guess it still is.
>
>
>
HI there,
I have asked this question, however I asked it under a different and
resolved topic, so I posted the quest under a more suitable title. I hope
thats ok
We have tried to configure two compute server nodes one of which is running
on a weaker machine. The node running on the more powerful
Hi!
IgniteQueue is stored in the atomics cache, which is called
ignite-sys-atomic-cache@default-ds-group by default.
This cache is stored in the default data region, so in order to make it
persisted, you need to make the default data region persisted using
Hello,
Thank for reply.
in my case terminated(kiiled) all ignite server pods manually in that case
all Nodes will left the cluster and client node should terminate and it will
raise the event CLIENT_NODE_DISCONNECTED.
if any one server get disconnected then event NODE_LEFT event will raise and
17 matches
Mail list logo