Dmitry Sherstobitov created IGNITE-10878:
Summary: "Failed to find completed exchange future" error occurs
in test with round cluster restart
Key: IGNITE-10878
URL: https://issues.apache.org/jira/browse/IG
Ilya Kasnacheev created IGNITE-10879:
Summary: Create suite of Cassandra Cache Store tests, add to TC
Key: IGNITE-10879
URL: https://issues.apache.org/jira/browse/IGNITE-10879
Project: Ignite
Alexey, thanks for your support.
Answer to your questions:
1) At the moment the types are: String, Long and Double. But this could
actually change in the future to any other user-defined types/classes (We
know we would need to provide data encoders for such types)
2) Yes, all data series have the
Thanks a lot for the example. Will write later about keepBinary support in
this thread.
чт, 10 янв. 2019 г. в 13:28, otorreno :
> Alexey, thanks for your support.
>
> Answer to your questions:
> 1) At the moment the types are: String, Long and Double. But this could
> actually change in the futur
Igniters,
As you know, Ignite logs configuration tuning suggestions at node
startup to improve performance.
At the moment, it recommends using Java 8 even if later releases are used.
Public updates will not be available for business users since January
of 2019 if I'm not mistaken.
It may be use
Eduard Shangareev created IGNITE-10880:
--
Summary: Document how we should evolve our persistence
functionality while keeping it compatible with files created by old versions
Key: IGNITE-10880
URL: https://issu
Stanilovsky Evgeny created IGNITE-10881:
---
Summary: Normalize QueryEntities if cache in restarting state need
to be refactored.
Key: IGNITE-10881
URL: https://issues.apache.org/jira/browse/IGNITE-10881
Ilya Kasnacheev created IGNITE-10882:
Summary: .Net PartitionLoss tests are flaky after NPE is fixed in
CachePartitionPartialCountersMap
Key: IGNITE-10882
URL: https://issues.apache.org/jira/browse/IGNITE-1088
Hi Igniters,
After removal of GitHub Comments from the list I have (a very subjective)
feeling, that there became more human-human interaction, which is
definitely more important that opportunity to control new JIRA tickets
using the list.
I suggest coming back to the idea of moving JIRA to a sep
I feel the first step there should be to switch our tests running on TC to
java > 8.
After some time having newer java as default we can change suggestions for
users.
чт, 10 янв. 2019 г. в 14:08, Vyacheslav Daradur :
> Igniters,
>
> As you know, Ignite logs configuration tuning suggestions at no
AFAIK some test-agents are configured to use JDK 9/10/11, isn't it?
On Thu, Jan 10, 2019 at 2:59 PM Dmitriy Pavlov wrote:
>
> I feel the first step there should be to switch our tests running on TC to
> java > 8.
>
> After some time having newer java as default we can change suggestions for
> use
Yes, and we can run tests on J9,10,11 but it is controlled by JavaHome
build parameter during runAll start. I suggest first to change this
parameter as default to newer Java in 2-4 weeks before updating our
recommendations.
чт, 10 янв. 2019 г. в 15:10, Vyacheslav Daradur :
> AFAIK some test-agent
Dmitriy Govorukhin created IGNITE-10883:
---
Summary: IgniteRebalanceOnCachesStoppingOrDestroyingTest flaky
failed in PDS4
Key: IGNITE-10883
URL: https://issues.apache.org/jira/browse/IGNITE-10883
Ilya Kasnacheev created IGNITE-10884:
Summary: Failure to perform non-MVCC SQL from transactions
Key: IGNITE-10884
URL: https://issues.apache.org/jira/browse/IGNITE-10884
Project: Ignite
Ilya Kasnacheev created IGNITE-10885:
Summary: Yardstick scripts refer to nonexistent OffHeap benchmarks
Key: IGNITE-10885
URL: https://issues.apache.org/jira/browse/IGNITE-10885
Project: Ignite
Dmitrii,
See my comments at issue.
Next time, please leave review request inside the issue.
On Wed, Jan 9, 2019 at 6:39 PM Dmitrii Ryabov wrote:
> Hi,
>
> Anton, can you review ticket for examples [1]?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-6826
>
> пн, 24 дек. 2018 г., 15:23 Anto
Mikhail Cherkasov created IGNITE-10886:
--
Summary: JVM_OPTS and -J-PARAMS doesn't allow spaces
Key: IGNITE-10886
URL: https://issues.apache.org/jira/browse/IGNITE-10886
Project: Ignite
Is
Hello!
I've merged this to master. Now we should to try run nodes in UTF-8 mode
unless specified otherwise explicitly.
Also added a warning on start-up if other encoding is used as it might lead
to data corruption.
Regards,
--
Ilya Kasnacheev
ср, 26 дек. 2018 г. в 19:25, Dmitriy Pavlov :
> +
Dmitriy,
This does not look like a production-ready case :)
How about
1) Once you need to write an entry - you have to chose not random "page
from free-list with enough space"
but "page from free-list with enough space closest to the beginning of the
file".
2) Once you remove entry you have to m
Hello!
I have a concern about MetaStorage - it uses default system encoding to
serialize keys. This means that after this change Windows nodes won't be
able to read previous MetaStorage files.
Is that OK? Is there a way to migrate old MetaStorages safely?
чт, 10 янв. 2019 г. в 16:57, Ilya Kasnac
Hello!
I'm afraid not, but it is still possible to force legacy encoding as a
workaround.
Is there an expectation that MetaStorage contains I18N keys?
Regards,
--
Ilya Kasnacheev
чт, 10 янв. 2019 г. в 17:11, Ivan Bessonov :
> Hello!
>
> I have a concern about MetaStorage - it uses default sy
I believe that all current keys are just basic English strings and it's too
early to say that current change breaks something, sorry.
We just have to ensure that old cp-1251 MetaStorages work fine and
maybe then force UTF-8 for MetaStorage in source code to avoid such
problems in the future. What
Hello!
I'd force UTF-8 where possible. It should not be very hard to write a test
to ensure that an old one works (using multijvm).
Regards,
--
Ilya Kasnacheev
чт, 10 янв. 2019 г. в 17:21, Ivan Bessonov :
> I believe that all current keys are just basic English strings and it's too
> early to
+1 for j...@ignite.apache.org
On Thu, Jan 10, 2019 at 6:55 PM Dmitriy Pavlov wrote:
> Hi Igniters,
>
> After removal of GitHub Comments from the list I have (a very subjective)
> feeling, that there became more human-human interaction, which is
> definitely more important that opportunity to co
Hi Igniters,
What do you think about the drop Scala 2.10 support?
Currently, we support two versions of Scala - 2.10 and 2.11, I suggest to
drop 2.10 and use only 2.11. Originally we have the old version of Scala
for supporting old versions of Apache Spark.
But support for Scala 2.10 was removed
+1 to drop support of Scala 2.10 in Ignite 2.8.
On Thu, Jan 10, 2019 at 9:59 PM Yuriy Babak wrote:
> Hi Igniters,
>
> What do you think about the drop Scala 2.10 support?
>
> Currently, we support two versions of Scala - 2.10 and 2.11, I suggest to
> drop 2.10 and use only 2.11. Originally we h
+1 for moving JIRA notifications out of dev-list. No strict opinion
which list should be a destination for them, I am fine with both
options.
By the way Community Resources page [1] refers to 2 another lists
iss...@ignite.apache.org and comm...@ignite.apache.org (but
notificati...@ignite.apache.or
I'm using comm...@ignite.apache.org to track who and what commits to
master :)
--
Alexey Kuznetsov
A bit of background:
When TcpDiscoverySpi is used, TcpDiscoveryMetricsUpdateMessage is sent by a
coordinator once in metricsUpdateFrequency, which is 2 seconds by default.
It serves as a ping message, which ensures, that the ring is connected, and
all nodes are alive. These messages have a high pri
+1
I think, a separate list for JIRA notification is needed,
as they are more important, than other ones.
notificati...@ignite.apache.org may still aggregate all automatically
generated
messages from all sources.
So, I'm for stopping sending JIRA messages to the dev list, and sending them
to noti
Stanislav Lukyanov created IGNITE-10887:
---
Summary: Docs: Align performance tips for .Net with Java
Key: IGNITE-10887
URL: https://issues.apache.org/jira/browse/IGNITE-10887
Project: Ignite
Hello!
I don't see why we can't. Just take it over, run tests, move to PA, etc.
Regards,
--
Ilya Kasnacheev
чт, 3 янв. 2019 г. в 17:00, Dmitriy Pavlov :
> Hi Igniters,
>
> I'm trying to reach the author of the fix because the ticket is still in In
> Progress.
>
> Could you please advice me ho
Vyacheslav Daradur created IGNITE-10888:
---
Summary: .NET: ServicesTest.TestGetServiceProxy(False) became
flaky with high fail rate
Key: IGNITE-10888
URL: https://issues.apache.org/jira/browse/IGNITE-10888
Looks like the test "ServicesTest.TestGetServiceProxy(False)" became
flaky after IGNITE-9607.
I muted the test on TC and filled Jira issue assigned to myself:
https://issues.apache.org/jira/browse/IGNITE-10888
On Mon, Jan 7, 2019 at 2:37 AM wrote:
>
> Hi Igniters,
>
> I've detected some new iss
Denis,
Correct me in case I got it all wrong.
Since metrics are scheduled, a possible situation is to have more than 1
TcpDiscoveryMetricsUpdateMessage inside the queue due to slow ... some
reasons.
Proposed solution looks like a fix hides the real problem.
My proposal is
1) Write a warning mess
+1
On Thu, Jan 10, 2019 at 6:02 PM Alexey Kuznetsov
wrote:
> +1 to drop support of Scala 2.10 in Ignite 2.8.
>
>
> On Thu, Jan 10, 2019 at 9:59 PM Yuriy Babak wrote:
>
> > Hi Igniters,
> >
> > What do you think about the drop Scala 2.10 support?
> >
> > Currently, we support two versions of Sca
+1
чт, 10 янв. 2019 г. в 19:09, Anton Vinogradov :
> +1
>
> On Thu, Jan 10, 2019 at 6:02 PM Alexey Kuznetsov
> wrote:
>
> > +1 to drop support of Scala 2.10 in Ignite 2.8.
> >
> >
> > On Thu, Jan 10, 2019 at 9:59 PM Yuriy Babak wrote:
> >
> > > Hi Igniters,
> > >
> > > What do you think about t
Ilya,
It's really hard question. Generally fail-fast principle is a good
idea. Ignoring every error can lead to real damage.
But in fact it is very general statement. Pure fail-fast sounds not
good solution for a server application which should work stable for
many hours. And nobody is free from
Denis, what if we remove priority difference for messages and always add
new to the end of the queue?
As far as traversing the queue - I don't like O(n) approaches =). So, with
adding all messages to the end of the queue (removing prio difference) I
would suggest that we save latest 1st lap messag
I see that we're getting around 150 scala_2.10 downloads monthly. Is there
any other component which uses it? I would remove the module in 3.0 to not
break the compatibility.
--
Denis
On Thu, Jan 10, 2019 at 8:13 AM Nikolay Izhikov wrote:
> +1
>
> чт, 10 янв. 2019 г. в 19:09, Anton Vinogradov :
-1 for this action.
JIRA notifications are sent on purpose to the dev list - someone came
across an issue and want to report it to the dev community. The community
has to be aware of this. That's the purpose of the community to improve and
fix the project. It's just wrong to force to subscribe to
Hi Dmitriy,
Ilya has created following jira issue to address the problem
https://issues.apache.org/jira/browse/IGNITE-10879
We will need to create a TestSuite for cassandra store and also include
this following test which will help in validation
IgnitePersistentStoreTest
Regards,
Saikat
On W
Alexey Kuznetsov created IGNITE-10889:
-
Summary: Web Console should work with Web Agent started from
Docker image.
Key: IGNITE-10889
URL: https://issues.apache.org/jira/browse/IGNITE-10889
Project
Ok, Denis, Thank you for sharing your vision.
BTW, we have now separate list for archiving all JIRA actions here
https://lists.apache.org/list.html?iss...@ignite.apache.org I didn't know
about it before yesterday. This probably proves that newcomers will ignore
a separate list.
пт, 11 янв. 2019 г
Denis,
We have long discussion about that (see above). And general consensus is
that typical contributor is not interested in majority of automated
messages. All updates except of "ticket created" are already routed to the
separate list for a long time. This JIRA list contains important
notificati
Hi Stan,
The thing is that index rebuild when node is not operational might be order
of magnitude faster than rebuilding an index when node is online. This is
the only reason why I thought the third option is worth considering.
Vladimir.
On Wed, Dec 19, 2018 at 5:32 PM Stanislav Lukyanov
wrot
Vladimir,
Personally, I treat ticket creation in JIRA as an alternate action for a
new dev list discussion when a task is not severe, and there is no need to
start an explicit conversation. Someone wants the dev community to be aware
of a task or issue, hoping that ownership will be taken soon. Ye
47 matches
Mail list logo
