Finally found the issue.
In the thin client configuration I had only one port provided to connect
to the server nodes. As soon as I provided the default range
(10800-10900) the connections seemed to behave better. This resolved the
issue somehow.
However I tried it out at the cluster on the
Hi,
today I tried to use the thin client to connect to two server nodes and
test the performance.
Basically I tried to push random data from nodes where the Ignite
database is not running.
I used the put_all method of the c++ thin client api to do that with
concurrent threads.
However
Hi,
the CAP Theorem states that a database can only achieve two of the
following design goals:
- Availability
- Consistency
- Partition Tolerance
Which two of the above design goals Apache Ignite has been developed for?
Mongo DB and Redis for instance match Consitency and Partition
Hi,
another issue popped up.
SQLRowCount gives me back 0 when I execute the following query:
select * from mytable limit 10;
The column count is correct. The rowcount not as the api is fetching 10
rows
I honestly think what I've seen so far is that the current ODBC driver
implementation in
Hi,
after spending several hours to get the unixodbc driver up and running I
nearly gave up.
However together with the author of unixodbc I was able to find out that
the current odbc driver in Apache Ignite is not doeing what it's
supposed to do.
As soon as I execute the command:
et =
The code I'm using at the moment is here...
https://filebin.ca/5ihkjcOx8nid
Am 26.11.20 um 7:41 PM schrieb Wolfgang Meyerle:
Hi,
I'm now trying to connect to apache ignite via the odbc driver the whole
afternoon and now I'm stuck.
The compilation and the installation in the platform/cpp
Hi,
I'm now trying to connect to apache ignite via the odbc driver the whole
afternoon and now I'm stuck.
The compilation and the installation in the platform/cpp directory went
fine. Unixodbc driver was successfully installed according to the readmes.
I also double checked dependency
Hi,
I tried to run apache ignite as given by example from the website as a
server node attached to my cpp program.
Basically it works fine but debugging is not possible anymore which is a
show stopper. The application crashes everytime when the program is
debugged in QT.
Any suggestions?
Hi,
I tried using
ignitevisorcmd.sh -cfg=
however I'm getting the following error message:
Local node's binary configuration is not equal to remote node's binary
configuration
It further states:
localBinaryCfg=null
rmtBinaryCfg={globIdMapper ...
I'm using the exact same xml configuration
Hi community,
I have a question regarding the xml configuration which is used in
clients / servers and thinclients.
Is it really necessary that each node is using the same configuration?
I'm just asking because I'm trying out to setup multiple servers in one
machine which totally is nonsense
Hi,
Is it possible somehow to define specific Java VM Parameters through the
cpp interfacte or the xml configuration files.
I'm facing serious sys-stripe timeouts and one recommendation of Ignite
is to switch to IPv4 only.
Unfortunately this is an Java VM Parameter which I do not seem to
n
*Gesendet:* Montag, 16. November 2020 12:10
*An:* user
*Betreff:* Re: Thin Client connection not working...
Doesn’t work how? Doesn’t compile? Doesn’t connect? Doesn’t create the
cache? Is there an error?
> On 16 Nov 2020, at 09:57, Wolfgang Meyerle
wrote:
>
> Hi,
>
> I t
?
Is there an error?
> On 16 Nov 2020, at 09:57, Wolfgang Meyerle
> wrote:
>
> Hi,
>
> I tried using the cpp thin client example from the Apache ignite site to
> create a small thin client connection example to one of the running Apache
> Ignite cluster nodes.
>
?
> On 16 Nov 2020, at 09:57, Wolfgang Meyerle
> wrote:
>
> Hi,
>
> I tried using the cpp thin client example from the Apache ignite site to
> create a small thin client connection example to one of the running Apache
> Ignite cluster nodes.
>
> However it does
Hi,
I tried using the cpp thin client example from the Apache ignite site to
create a small thin client connection example to one of the running
Apache Ignite cluster nodes.
However it doesn't work and I'm out of a clue.
I added the following bean to my persistence configuration file:
Hi,
I have a question in regards to Apache Ignite performance tuning.
This is my config so far:
https://pastebin.com/NWDzY3RK
I plan to store 2 billion entries in the database. The machine that I
have is not great, 32gb ram nothing more.
I wonder how I can tune the performance to speed up
Hi,
I'm trying to change the xml configuration in apache ignite to support
SQL for data caches:
see https://pastebin.com/4qtepp0A
However this config file doesn't seem to work.
If I comment out the cache configuration part it works.
What's wrong with it? Can't I mix cache configuration and
Another question according a proper shutdown of ignite.
Do I have to catch the sigint signal to properly shutdown apache ignite
in my environment and set the node to inactive or is the code in ignite
catering for this itself? Is it safe to install signal handlers with the
usage of the ignite
Hi,
I have a question where I'm currently struggling to find the answer in
the Ignite Documentation and hopefully somebody of you can guide me in
the right direction.
According to the Ignite DDL Documentation of SQL I'm able upon Table
creation to provide a cache name and I have a keyname
Hi,
I'm currently struggling a little bit getting Ignite up and running with
UnixOdbc on my OSX machine.
I'm compiling the platform cpp files atm with
cmake -DWITH_ODBC=ON -DWITH_THIN_CLIENT=ON -DWITH_TESTS=ON
-DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/Users/user/ApacheIgnite ..
20 matches
Mail list logo
