Hi Val,
I have attached the sample program. please take a look and let me know if
you have any questions.
after spending some time, i noticed that the exception is happening only
when processing of number of parallel callable's with broadcast.
Thanks,
Anil
On 15 October 2016 at 04:33,
I think you should check the network. Numbers do not sound right to me.
You can't also try adding more servers and clients to split the load.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Poor-GET-performance-tp8319p8333.html
Sent from the Apache Ignite
switching to PRIMARY_SYNC configuration, PUT benchmarks dropped to 35K
ops/sec.
I dont think its a memory issue, because heap is configured to 10GB and
entries are stored off-heap with Non-Heap memory set to unlimited. The
server has 28GB and plenty of available memory.
Follows are the JVM
you mean Ignite logs or GC logs?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Poor-GET-performance-tp8319p8328.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi,
Can you attach full log files from all nodes?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/AssertionError-tp8321p8327.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi
I mean using HTTPS transport instead of binary (thrift?) transport.
2016-10-17 19:10 GMT+02:00 Igor Sapego :
> Hi Vincent,
>
> Can you please explain what do you mean by HTTP(S) support for the ODBC?
>
> I'm not quite sure I get it.
>
> Best Regards,
> Igor
>
> On Thu,
Thanks for the advice.
Recommendations to tune JVM are already applied in our benchmarks. I will
repeat the test using PRIMARY_SYNC and see how it goes.
Do you think the GET benchmarks are reasonable? Am i hitting the limit?
compared to Redis or Couchbase the GET figures are v. low. Is it this
Hi,
First of all, I would not recommend to use FULL_ASYNC mode for updates. This
mode means that you don't wait for update to happen, i.e. even if it fails,
you won't know about this. This is also bad for benchmarks, because you
don't take into account the time that is actually spent for update
Hi Vincent,
Can you please explain what do you mean by HTTP(S) support for the ODBC?
I'm not quite sure I get it.
Best Regards,
Igor
On Thu, Oct 6, 2016 at 9:59 AM, vincent gromakowski <
vincent.gromakow...@gmail.com> wrote:
> Thanks
>
> Starting the thriftserver with igniterdd tables doesn't
Hello,
I get the below exception occasionally. It renders the client unusable. The
setup is as follows:
#3 server nodes
#1 Client node
I usually see this (Not always) when one of the server nodes is started
after the client is up.
10:39:38,355 SEVERE [TcpDiscoverySpi] Runtime error caught
Thank you very much. Will give it a shot and let you know of any issues.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/DataStreamer-pool-tp5857p8320.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi,
It is look like correct implementation.
How do you come to conclusion, which something wrong?
On Mon, Oct 17, 2016 at 6:29 AM, minisoft_rm
wrote:
> Hi Val,
> the reason is that "assignPartitions()" returns same
> "List" usually even I start two ignite
12 matches
Mail list logo