Agree. I brought the section back because there was a broken link, and I
believe I removed it earlier by mistake. We definitely should add more
details though.
-Val
On Wed, May 12, 2021 at 9:20 AM Dmitry Pavlov wrote:
> Hi Denis,
>
> +1 from my side.
>
> Now extensions in the download page look
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*New Critical Failure in master RDD
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Rdd?branch=%3Cdefault%3E
No changes in the build
- Here's a reminder o
Hi Denis,
+1 from my side.
Now extensions in the download page looks like a bit incomplete snippet of code.
It is better than nothing, but completed table would look better.
Sincerely,
Dmitriy Pavlov
On 2021/05/12 14:02:04, Denis Magda wrote:
> Igniters, Val,
>
> I came across the Extensio
+1
Without awareneess, on the contrary, we can get huge memory utilization on one
server node.
With awareness we're more scalable on that matter.
Sincerely,
Dmitriy Pavlov
On 2021/05/12 15:39:53, Igor Sapego wrote:
> +1 from me. There were no major issues with this feature and it gives
> g
+1 from me. There were no major issues with this feature and it gives
good performance boost for many cases.
Best Regards,
Igor
On Wed, May 12, 2021 at 5:18 PM Ivan Daschinsky wrote:
> Huge +1 from me. PA should be enabled by default.
>
> ср, 12 мая 2021 г. в 13:33, Pavel Tupitsyn :
> >
> > Ig
Dear Ignite Community,
I have uploaded a release candidate of the following extension modules:
spring-data-commons
spring-data-ext
spring-data-2.0-ext
spring-data-2.2-ext
The release candidate of the extensions:
spring-data-commons
https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions
Dear Ignite Community,
I have uploaded a release candidate of the performance-statistics-ext
extension module.
The release candidate of the performance-statistics-ext extension:
https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-performance-statistics-ext/1.0.0-rc3/
The instr
Huge +1 from me. PA should be enabled by default.
ср, 12 мая 2021 г. в 13:33, Pavel Tupitsyn :
>
> Igniters,
>
> Partition Awareness (PA) is implemented in 5 out of 6 thin clients [1].
>
> However, this feature is disabled by default in most clients for
> compatibility reasons:
> initially we only
Igniters, Val,
I came across the Extensions section that was restored on the downloads
page. It looks clumsy, broken, and incomplete. We're listing spring boot
artifacts without any reference to other modules:
https://ignite.apache.org/download.cgi#extensions
How about:
- Removing the code sn
Hi Ilya,
Welcome to Apache Ignite Community!
I added your account to contributors list in JIRA. Now you can assign
ticket to yourself.
2021-05-12 16:29 GMT+03:00, Ilya Korol :
> Hello Ignite Community!
>
> My name isIlya Korol. I want to contribute to Apache Ignite. My JIRA
> username*Korol*.
>
Hello Ignite Community!
My name isIlya Korol. I want to contribute to Apache Ignite. My JIRA
username*Korol*.
Thanks!
Hi!
I propose to add a new MBean linked to DMS that contains the property
IGNITE_PDS_WAL_REBALANCE_THRESHOLD.
That enables configuration through JMX.
WDYT?
On Tue, 11 May 2021 at 16:52, Eduard Rakhmankulov
wrote:
> Hi Stanislav,
>
> I think this is an excellent idea to use distributed metasto
Igniters,
Partition Awareness (PA) is implemented in 5 out of 6 thin clients [1].
However, this feature is disabled by default in most clients for
compatibility reasons:
initially we only used one connection to the cluster, but with PA enabled
we establish
connections to every server node, which
Hi Raymond,
Following comes to my mind as a workaround. If you need to build only
kubernetes module you can specify it directly with mvn command
arguments.
mvn clean install -Pall-java,all-scala,licenses -DskipTests -pl
modules/kubernetes -am
Or possibly exclude only jta module from build.
mvn
14 matches
Mail list logo