Alexey,
Thank's for keeping an eye on page updates.
Near Caches is not a bad feature, but it should be used with caution.
At least we have to explain how it works on readme.io, why and when it
should be used because usage can drop the performance instead of increasing
it.
Anyway, I added near
Folks,
During investigation of thin client test suite failures [1] I found
that it is not clear whether --add-modules=java.transaction in
ignite.sh/bat is needed (we add this module for Java 9 and 10). In
thread [1] I already mentioned that launching ignite.sh with Java 9
and ignite-jta libraries
Hello, Alexey.
Thanks for the feedback!
> My only concert is that we should have the metrics framework configuration
> as the first-citizen of the framework itself
Yes. I planned to add `void configure(String param)` method to the metric API.
> but change the metrics parameters in
> runtime
Hi Anton,
I will take a look at your pull request if you don't mind.
In any way, could you please update the IEP page with the list of
constraints/limitations of the proposed approach, TODOs, etc?
For instance, I would like to see all these limitations on the IEP page as
JIRA tickets. Perhaps,
Slava,
>> I will take a look at your pull request if you don't mind.
Great news!
>> In any way, could you please update the IEP page with the list of
>> constraints/limitations of the proposed approach, TODOs, etc?
Not sure we should keep this at IEP until list (#4 from original letter) is
not
Igor,
The user prefers using SQL syntax which is widespread. For sure, we'll
recommend alternate solutions as long as INSERT is not suited for loading
if a thin client is used.
However, how have we supported the streaming mode for INSERTS for ODBC?
Isn't it already based on the thin client
Alex,
I would do an email survey to hear an opinion of why someone believes a
feature A has to stay. It makes sense to ask about the APIs to be removed
as well as integrations to go out of community support [1] in the same
thread.
Has everyone expressed an opinion? If yes, I can go ahead and
Ivan Pavlukhin created IGNITE-11946:
---
Summary: Do not add java.transaction module in Ignite launch
scripts
Key: IGNITE-11946
URL: https://issues.apache.org/jira/browse/IGNITE-11946
Project: Ignite
If they use python client, why wont they just use put_all()?
To me it just looks like they are using wrong tool here.
As for your questing, Affinity Awareness for thin clients is only for Cache
API now, it does not affect SQL.
Best Regards,
Igor
On Thu, Jun 27, 2019 at 7:33 PM Denis Magda
Anton, good point.
Do you have any idea how we can keep track of the voting? Should we launch
a google survey or survey monkey? Voting by email?
пт, 28 июн. 2019 г. в 11:24, Anton Vinogradov :
> Alexey,
>
> Thank's for keeping an eye on page updates.
> Near Caches is not a bad feature, but it
Hello, Igniters.
I see that the ticket - "[IGNITE-11848] New Monitoring. Phase1" breaks
cache stop performance. It affects next tests: testParallelStartAndStop,
testStartManyCaches
The spent time was increased 6 times:(
Look at:
Hello Nikolay,
>From the latest TC runs I can see a sporadic regression
in testParallelStartAndStop and testStartManyCaches tests. Digging deeper,
I see that stopping a single cache when there are many other started caches
now takes a significant amount of time.
Current suspect is
Hello, Maksim.
I will take a look shortly.
В Пт, 28/06/2019 в 19:02 +0300, Maksim Stepachev пишет:
> Hello, Igniters.
>
> I see that the ticket - "[IGNITE-11848] New Monitoring. Phase1" breaks cache
> stop performance. It affects next tests: testParallelStartAndStop,
> testStartManyCaches
>
Sorry for the duplicate - apparently, Maksim also spotted this regression.
Let's continue the discussion in the separate thread.
пт, 28 июн. 2019 г. в 19:04, Alexey Goncharuk :
> Hello Nikolay,
>
> From the latest TC runs I can see a sporadic regression
> in testParallelStartAndStop and
Hello, Alex.
I will fix it shortly.
Ticket - https://issues.apache.org/jira/browse/IGNITE-11945
В Пт, 28/06/2019 в 19:04 +0300, Alexey Goncharuk пишет:
> Hello Nikolay,
>
> From the latest TC runs I can see a sporadic regression in
> testParallelStartAndStop and testStartManyCaches tests.
Nikolay Izhikov created IGNITE-11945:
Summary: [IEP-35] Performance drop on cache stop
Key: IGNITE-11945
URL: https://issues.apache.org/jira/browse/IGNITE-11945
Project: Ignite
Issue
16 matches
Mail list logo
