Ok guys, just updated the documentation.
Igor
On Thu, Dec 1, 2016 at 4:44 PM, Igor Rudyak wrote:
> Hi Riccardo,
>
> Thanks for noticing this. That's a documentation issue. There were number
> of refactorings for Ignite-Cassandra and documentation now is not 100% up
> to
Hi Val,
I think No. Correct me if i am wrong.
i was looking at following code pieces -
1. JdbcResultSet#next()
try {
JdbcQueryTask.QueryResult res =
loc ? qryTask.call() :
ignite.compute(ignite.cluster().forNodeId(nodeId)).call(qryTask);
hi,
I have found that ignite-spark-1.7.0 doesn't support spark 2.0.x. Does
it support spark 1.6.x?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Can-ignite-spark-support-spark-1-6-x-tp9358.html
Sent from the Apache Ignite Users mailing list archive at
Hi, Igor:
You said before that you are working on extending C++ API?? can you tell
me when extending C++ API can be released?
Thank you very much!
-- --
??: "Igor Sapego";;
: 2016??11??8??(??)
Igniters,
I’ve finished reworking, enhancing and expanding our SQL Grid documentation
preparing it to 1.8 release.
If you recall, before it was a single page documentation and now it’s a big
section that contains, I hope, all the valuable knowledge we can share with
Ignite users. Just open
Vidhya,
Are you using Spring Cache? Because that's what this issue is about. I'm not
sure how this is related to your use case.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/SparkRDD-with-Ignite-tp9160p9354.html
Sent from the Apache Ignite Users mailing
Hi Val,
No, that's not the issue. I would like to follow the AWS ignite-cassandra
framework guide on the documentation, but some files the documentation says
I should modify are not in the test-package after I build ignite from
source.
Just to be clear, this is the link to the guide I am
Ganesh,
I'm not I understand what you mean here. There is no such a delay, indexes
on new node are created right away and updated during the rebalancing. There
is no way indexes are temporarily not used due to topology change. If there
is a slowdown, most likely it's caused by the rebalancing
Hi,
First of all, remove the ipFinder.setShared(true); line. With this nodes
will join each other if VmIpFinder is used.
If this doesn't help, please look through the logs and check which address
and port discovery binds to and compare it to address you provide in IP
finder. This should give you
Anil,
This means that you stopped the embedded client node before it loaded all
the data into the cache. Ignite and IgniteDataStreamer provided via
setIgnite() and setStreamer methods should not be closed before the Kafka
streamer is closed.
See the example here:
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.
xjg125 wrote
> I test the DeploymentSpi ,
> refer to the
Vidhya,
I'm not aware of this issue, but it sound pretty serious. Are there any
ticket and/or discussions about this you can point me to?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/SparkRDD-with-Ignite-tp9160p9345.html
Sent from the Apache Ignite
Ganesh,
Can you grab a thread dump? What are these threads doing?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Unable-to-establish-connection-to-Ignite-server-System-Thread-Pool-Issue-tp9294p9344.html
Sent from the Apache Ignite Users mailing list
BinaryObjectImpl is a binary object, while deserialized objects will be shown
as your classes. Deserialized objects are not stored by default. However, if
you have queries enabled, and do a read on server side (i.e. send a closure
there to do a local get), then the deserialized object will be
Anil,
While you iterate through the ResultSet on the client, it will fetch results
from server in pages. Are you looking for something else?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Fetching-large-number-of-records-tp9267p9342.html
Sent from the
Hi Yuci,
Basically, this error means that affinity function on node A gave node B as
a primary node for a key. Node A than sent a request to node B, but affinity
on node B doesn't think that this key belong locally. In other words,
affinity function worked inconsistently on different nodes.
Hi Sam,
Can you create a small project on GitHub with instructions how to run? I
just tried to repeat the same test, but everything works fine for me.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Cluster-hung-after-a-node-killed-tp8965p9340.html
Sent
Hi Yuci,
1.8 in in final testing/bug fixing stage, so it should become available
soon. However, "Failed to wait for initial partition map exchange" is a very
generic error and can be caused by different circumstances. I would
recommend to build from 1.8 branch and run your tests on it ti check if
Hi Val,
Thanks for pointing out the errors.
Since i was getting errors related to GC pauses, I had set offHeapMaxMemory
to 0 as per the below link.
http://apacheignite.gridgain.org/docs/performance-tips#tune-off-heap-memory
But now i have set it to -1
After doing the required changes and
Val,
I have reproduced this with simple program -
1. Node 1 - run example ExampleNodeStartup
2. Node 2 - Run a program which create a transaction cache and add 100K
simple entries.
cfg.setCacheMode(CacheMode.PARTITIONED);
Hi Kaiming,
^-- Public thread pool [active=80, idle=0, qSize=944]
There are long queue and 80 busy threads that seemd do no progress.
It looks like all of threads are blocked. Please, attach a thread-dump.
On Tue, Nov 29, 2016 at 6:40 AM, Kaiming Wan <344277...@qq.com> wrote:
> I can find the
Hi, Mohammad!
Tomorrow I will try with examples-ignite.xml and 4 server nodes with 1
backup.
And share my findings.
On Thu, Dec 1, 2016 at 1:36 AM, Mohammad Shariq
wrote:
> Hi Alexplz let me know if u got my question...or I need to explain
> more...
>
> For now can u
Hi,
Ignite stores date as it specify in marshaller. Binary marshaller was
configured by default.
In case, if Binary marshaller was specified, all internal works will be
processed in binary view (hence do not need to store java classes on
server).
If you want to use binary view in own code, you
Hi Vladislav,
We have the same issue, "Failed to wait for initial partition map exchange",
when stopping or restarting one of the nodes in our cluster. In other words,
when stopping or restarting just one of the nodes, the whole cluster screws
up, i.e., the whole cluster stops working.
Just had
Hi,
Our app is getting the following error messages. Wonder what is all about.
Should I go check the key.hashCode() implementations, but the log does not
point out which key it's talking about. What would the indication of this
message be: something seriously wrong with the cluster?
Many thanks,
Thanks. After importing same package on server and client side solved my
problem(initially i wrote class in client node instead of importing it).
But, I am still unclear about how ignite stores data
case I : In both Binary and serialized format, and de-serializes data when
required
case II :
Hi,
Is there any way we can differentiate between deserialized and binary
objects from heap dump? I want to get details about *how many deserialized
and how many binary objects* are present in heap dump. Is there any way we
can store data in only binary format instead of serialized data?
Hi Val,
Yes. results are fetched in pages only. But each execute query will return
the results of a page. correct ?
I am checking if there way that direct query parser stream is available to
client though jdbc driver. Hope this is clear.
Thanks
On 1 December 2016 at 04:34, vkulichenko
Hi,
I think in your case (when you configured "QueryEntity"), have not
necessary to copy classe (schema.jar) to a server. Ignite will by use
binary[1] format, and execute SQL (or other query) without deserialization.
But I definitly do not understand why it does not work...
You can to clarify
I have written a program to start ignite in separate jvms to form a
cluster.It is starting the Ignite,but could not form a cluster. It is
printing following log.
Failed to connect to any address from IP finder (will retry to join
topology every 2 secs): [/10.150.113.61:47500]
Below is my
Hi,
I am using KafkaStreamer to populate the data into cache.
i see following message in logs
java.lang.IllegalStateException: Grid is in invalid state to perform this
operation. It either not started yet or has already being or have stopped
Hi, Thomas,
Recently, I have fixed an issue, that can be a cause for such a behavior -
[1].
This fix is going to be available in the upcoming Apache Ignite 1.8.
[1] - https://issues.apache.org/jira/browse/IGNITE-4249
Best Regards,
Igor
On Wed, Nov 30, 2016 at 1:45 PM, thomastechs
I am trying to evaluate Cassandra and Ignite following the AWS deployment
guide in the documentation. I've built both Ignite 1.6 and 1.7 from source,
but in both cases the test package generated misses the configuration file
*bootstrap/aws/env.sh* I should modify according to the documentation.
Hi,
GridDhtAtomicCacheEntry represents cache entry. BinaryObject represents
serialized objects: entry keys and entry values.
GridH2ValueCacheObject, GridH2KeyValueRowOnHeap are index internal objects.
On Thu, Dec 1, 2016 at 10:13 AM, rishi007bansod
wrote:
> I have
34 matches
Mail list logo