Hi Prasad,
Can you please share logs from all nodes, so I can check what was happening
with a cluster before an incident? It would be great to see logs since
nodes start.
Thanks,
Evgenii
чт, 26 дек. 2019 г. в 11:42, Denis Magda :
> Let me loop in the Ignite dev list as long as I've not heard
Igor,
When you are saying that we should not allow the dialect changing, are you
referring to changes in runtime when a node is already up-and-running?
Generally, it will be more than enough if a dialect can be set statically
and globally -- the user selects the dialect for the entire cluster via
Ilya, no I see, thanks for the explanation. Agree with you, let's update
the versions of the dependencies to the latest.
-
Denis
On Thu, Dec 26, 2019 at 10:50 PM Ilya Kasnacheev
wrote:
> Hello!
>
> I have committed ignite-spring-data_2.2 to ignite-2.8.
>
> By bumping versisons I mean the
Excellent, I've submitted an in-memory computing essentials talk there as
well. I hope at least one of the talks is to be selected. Keeping fingers
crossed.
-
Denis
On Fri, Dec 27, 2019 at 10:41 AM Saikat Maitra
wrote:
> Hi,
>
> Thank you for sharing the link Denis. I have submitted a talk on
Hi,
Thank you for sharing the link Denis. I have submitted a talk on Data
Streaming.
Regards,
Saikat
On Wed, Nov 27, 2019 at 5:25 PM Denis Magda wrote:
> Igniters,
>
> There are many of us who are spreading the word about Ignite globally. Does
> anybody have any technical talk of moderate and
Hi Denis,
Yes, adding other form of contributions like help in answering user
questions, updating documents and reviewing code changes will certainly
help in learning and knowing the project better
We can also add this link for reference for open issues waiting for review,
this will help folks
Ivan Rakov created IGNITE-12510:
---
Summary: In-memory page eviction may fail in case very large
entries are stored in the cache
Key: IGNITE-12510
URL: https://issues.apache.org/jira/browse/IGNITE-12510
Ivan Rakov created IGNITE-12509:
---
Summary: CACHE_REBALANCE_STOPPED event raises for wrong caches in
case of specified RebalanceDelay
Key: IGNITE-12509
URL: https://issues.apache.org/jira/browse/IGNITE-12509
Ivan Rakov created IGNITE-12508:
---
Summary: GridCacheProcessor#cacheDescriptor(int) has O(N)
complexity
Key: IGNITE-12508
URL: https://issues.apache.org/jira/browse/IGNITE-12508
Project: Ignite
Ivan Rakov created IGNITE-12507:
---
Summary: Implement cache size metric in bytes
Key: IGNITE-12507
URL: https://issues.apache.org/jira/browse/IGNITE-12507
Project: Ignite
Issue Type:
Hello.
Ivan is right that "baseline auto-adjust" is disabled by default if you start
your node on
existing PDS. But "baseline auto-adjust" is enabled by default for in-memory
cluster due to in-memory nodes also have bound to baseline since 2.8 version.
Also, I want to note that after this
Denis,
> Is it true that Calcite can parse MySQL, Oracle
Yes, it can.
> Do I need to select a dialect globally or can it be set on a per-query
> level?
Technically a parser, a validator, a planner, other components are created and
configured for each query call (because they are stateful). So
Hello,
"baseline auto-adjust" is disabled by default if you start your node on
existing PDS.
It's enabled on new clusters only.
Existing installations should not be affected by the update. Is that ok?
пт, 27 дек. 2019 г. в 14:46, Maxim Muzafarov :
> Ilya,
>
> +1 from my side.
>
> On Fri, 27
Ivan Bessonov created IGNITE-12506:
--
Summary: Deadlock in
DistributedMetaStoragePersistentTest.testUnstableTopology
Key: IGNITE-12506
URL: https://issues.apache.org/jira/browse/IGNITE-12506
Project:
Hello!
I have filed a ticket about this improvement, plan to start on coding.
https://issues.apache.org/jira/browse/IGNITE-12505
Regards,
--
Ilya Kasnacheev
чт, 26 дек. 2019 г. в 12:50, Ilya Kasnacheev :
> Hello!
>
> Okay, I will mark default region.
>
> We already log information about
Ilya Kasnacheev created IGNITE-12505:
Summary: Improve logging of data regions on startup
Key: IGNITE-12505
URL: https://issues.apache.org/jira/browse/IGNITE-12505
Project: Ignite
Issue
Ilya,
+1 from my side.
On Fri, 27 Dec 2019 at 14:36, Ilya Kasnacheev wrote:
>
> Hello!
>
> I have also noticed that we have baseline auto-adjust enabled by default in
> 2.8 builds, and it breaks existing code in runtime:
> https://issues.apache.org/jira/browse/IGNITE-12504
>
> I propose to turn
Hello!
I have also noticed that we have baseline auto-adjust enabled by default in
2.8 builds, and it breaks existing code in runtime:
https://issues.apache.org/jira/browse/IGNITE-12504
I propose to turn auto-adjust off by default in 2.8 release. What do you
think?
Regards,
--
Ilya Kasnacheev
Ilya Kasnacheev created IGNITE-12504:
Summary: Auto-adjust breaks existing code, should be disabled by
default
Key: IGNITE-12504
URL: https://issues.apache.org/jira/browse/IGNITE-12504
Project:
Ilya Kasnacheev created IGNITE-12503:
Summary: Fix SSL configuration in Jetty REST: httpCfg assignment
Key: IGNITE-12503
URL: https://issues.apache.org/jira/browse/IGNITE-12503
Project: Ignite
Here are my two cents on the topic:
* Obviously it is bad to have two different management console utilities,
so visorcmd and control.sh should be merged into a single utility
* In my personal opinion, this utility should _not_ be interactive. In the
current state it is impossible to use
Hello!
Task IGNITE-12470 is ready.
https://issues.apache.org/jira/browse/IGNITE-12470
Please check this API.
Regards,
Ryzhov Sergei.
чт, 26 дек. 2019 г. в 18:50, Maxim Muzafarov :
> Ilya,
>
>
> I agree with you that there is no risk and spring-data-2.2 can be
> safely cherry-picked to the
22 matches
Mail list logo
