Thanks Denis.
I would try this approach. I expect Ignite node can be stopped and started
again in same jvm. In this listener, I would incorporate ignite.stop
(having ignite initially configured with lifecycle bean which would react
to stop event and flush any pending cache to db via store).
On Se
Set MAIN_CLASS environment variable referring to your class with Java’s main
method and execute ignite.sh. Your class needs to have the following code
snippet in order to process a segmentation event
ignite.events().localListen(new IgnitePredicate() {
@Override public boolean apply(Event eve
I take that point. However, for custom scripts, is there a way to listen to
segmentation event (please share name) and only from local node (local
listener?) and in response to that event we could initialize beans or
invoke our process.
On Sep 10, 2016 3:24 AM, "vkulichenko"
wrote:
> Hi,
>
> Yo
Data stored in an Ignite cache is always being serialized. There is no way to
avoid serialization routines.
If you’re not planning to use Ignite API over the local cache then I would
suggest using standard Java’s Map interface implementations.
—
Denis
> On Sep 9, 2016, at 4:51 PM, javastuff..
Hello,
It appears that entry is being serialized, eventhough cache is defined as
LOCAL. Below is the configuration I used -
1. It will be performance overhead, when object is not shared and kept
locally only.
2. It is losing state
Peter,
What kind of information you're looking for?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Thread-count-tp7636p7644.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi Val,
thank you for your hint!
I just found out that reducing public-thread-pool-size results in a lower
write-performance.
At least I could reproduce it.
Are there any other information out there besides
https://apacheignite.readme.io/docs/performance-tips ?
Kind regards,
Peter
2016-09-09
Saikat,
Do you have any issues with this request? It's actually an example from
configuration and it should work.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Re-Not-able-to-retrieve-data-from-cache-tp7622p7642.html
Sent from the Apache Ignite Users mai
Hi,
I agree. Can you create a JIRA ticket for this?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Remote-node-gc-pause-tp7632p7641.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Ravi,
As I said earlier in the thread, please provide your project so that we can
run it and reproduce the issue. This way we will be able to help you.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/LOOK-THORUGH-THIS-ERROR-tp6977p7640.html
Sent from the A
Hi,
You should use ignite.sh script shipped with Ignite to support this mode.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Segmentation-policy-tp7635p7639.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi Peter,
You can probably set connectorConfiguration to null to disable the REST
server at all (unless you need it, of course). Other than that, you used all
the settings that can influence the number of threads. Ignite is designed to
be a distributed system, so it doesn't allow to disable discov
Hi,
In my example Ignite moves entries that a loaded from the local store to the
cache. If an entry is not loaded yet then it will not be moved to the new
node and potentially will be lost.
I will prepare an example for you to demonstrate the problem.
--
View this message in context:
http://a
Hello Ignite-Community!
as some of you might have read, I'm using Ignite as local Off-heap caches
only.
I limited the discovery to localhost and therefore I don't need threads
which are just active to handle e.g. grid topics.
I would like to reduce the amount of threads to an minimum.
The Off-hea
Hi,
can you please confirm on segmentation policy. We have configured Restart
policy and I see this in logs. however, grid did not restart, rather it went
in segmentation.
We have our custom script to restart java process (Ignite node).
2016-09-09 12:14:26.162 BST [WARN] -
thread="disco-event-wo
yes i saw streamer and tried with maven dependencies by adding pom.xml but i
convert in java project and run the same. still the same error ?
i tried every possible way to face this error. I think there is bug in
method of loadCache() while integrating with multiple java classes and there
is no a
@Pawantlor,
Finally we merged all changes to master branch and uploaded Docker images.
See documentation for Docker image: https://hub.docker.com/
r/apacheignite/web-console-frontend
See documentation for deploying locally from sources:
http://apacheignite.gridgain.org/docs/web-console
http://ap
Hi,
We see following error in our grid quite frequently.
2016-09-09 09:36:12.458 BST [WARN] -
thread="tcp-disco-msg-worker-#2%MMEventOrchestratorGrid%" -
class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi" - Timed out
waiting for message to be read (most probably, the reason is in long
Thanks Val.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/OFFHEAP-VALUES-MODE-VISOR-CONSOLE-tp7601p7631.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi,
You are executing operation without transaction on transactional cache. In
that case transaction was created implicitly on each operation.
Transaction is needed if you need to execute several operation as one.
On Fri, Sep 9, 2016 at 12:35 PM, seyeony wrote:
> Hi,
> During the persistent st
Hi,
During the persistent store test (CacheAutoStoreExample.java from examples),
I removed (commented out) the Transaction statemements as follows:
//try (Transaction tx = ignite.transactions().txStart()) {
...
...
//tx.commit(
https://github.com/WENPIN1/BreakJava8TierComp
Frequently reproduce the AssertionError on Windows x64
Java(TM) SE Runtime Environment 1.8.0_101-b13 Oracle Corporation Java
HotSpot(TM) 64-Bit Server VM 25.101-b13
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/P
Hi Patrick,
I was not able to reproduce this issue neither under 8u51 nor on 8u101
under Mac using your code. Can you share the reproducer which does not use
Ignite with us when it's available?
2016-09-09 11:43 GMT+03:00 wbyeh :
> Val,
>
> It's definitely not an ignite issue.
> It's Oracle JDK8
Val,
It's definitely not an ignite issue.
It's Oracle JDK8 TieredCompilation bug.
We may test the git source to reproduce this issue and I have consolidate
the reproducer.
I'll upload it to the git soon.
-Patrick
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.co
Hi,
Yes, you need to use ScanQuery[1] over partition (look at the
setPartition(int)[1] method). The query will be iterate over entry in a
particular partition.
To aware which partitions are storing in local node, use the code snippet:
Affinity aff = ignite.affinity(cacheName);
ClusterNode locNod
Is it possible to iterate through all key values on primary partition of
the node on this node?
Thanks,
Yitzhak
On Fri, Sep 9, 2016, 02:28 vkulichenko
wrote:
> IgniteCache is Iterable, so you can just iterate through its contents.
>
> -Val
>
>
>
> --
> View this message in context:
> http://apa
26 matches
Mail list logo
