Sam,
NONE mode is something that should be used very accurately. It means what it
means - no rebalancing is happening when topology is changing, unless you
trigger the rebalancing manually. For example, if you have a cache with one
backup and you lose one of the nodes, you end up having only one
Hi Sam,
Ignite starts its own HTTP server for rest API, so it's definitely possible
when running in JBoss as well as anywhere else. You just need to add
ignite-rest-http module with dependencies to classpath and the endpoint will
start automatically.
If you're using Maven, add this to pom.xml:
I think Dmitry meant that indexes are updated synchronously with transaction
commit. However, note that SQL queries are currently not transactional, so
you can still get dirty reads in the result set.
-Val
--
View this message in context:
Sorry. I should also mention that we've overloaded discovery with an Spi. I
cut it from the config I posted to remove clutter. It works fine when we run
--net=host so I'm assuming that's not the problem.
--
View this message in context:
Hi Val,
Thanks for the response. The AddressResolver is pretty simple. It's
initialized with a map of internal to external IPs (currently the map has a
single entry). The the main getExternalAddress(final InetSocketAddress addr)
looks like this:
try {
LOGGER.debug("{} Looking
Hi Jim,
Please show you AddressResolver implementation, your configuration and
describe the deployment in more details (how many nodes, how addresses are
assigned to them, etc).
-Val
--
View this message in context:
Hello, fellow Apache enthusiast. Thanks for your participation, and
interest in, the projects of the Apache Software Foundation.
I wanted to remind you that the Call For Papers (CFP) for ApacheCon
North America, and Apache: Big Data North America, closes in less than a
month. If you've been
Hi,
Did I get you correct, that you want to send an update to a topic every
time the cache is updated?
If that is the question then I would suggest you taking a look at the
following:
https://apacheignite.readme.io/docs/events
https://apacheignite.readme.io/docs/messaging
On Wed, Jan 18, 2017
Yes, I pass the example xml, like this:
object RDDProducer extends App {
val conf = new SparkConf().setAppName("SparkIgnitePro")
val sc = new SparkContext(conf)
val ic = new IgniteContext(sc,"../examples/config/example-cache.xml")
val sharedRDD= ic.fromCache[Integer,Integer]("a")
val
Hi,
If you want to estimate a reason you need to use profile and after make a
conclusion.
You should to check your application (using flight recorder[1] for example)
and make a investigation where are threads stopping. How long do threads
spend time in parking state? What is reason of this?
This is the configuration. All just default.
localhost:47500..47509
Hi,
I have a task to compute on ignite. My Service has 8 cores. I split the task
into more than 1K jobs and merge the result.
>From client see, the task run more than 3 seconds, and sometimes more than
10 seconds. The ignite server load is very slow.
I wonder to know how to increase the CPU
12 matches
Mail list logo
