Re: Re: TPS does not increase even though new server nodes added
it's the full thread dumps ,the attarchment file name is 1.txt yu...@toonyoo.net From: Ilya Kasnacheev Date: 2019-03-04 15:32 To: user Subject: Re: TPS does not increase even though new server nodes added Hello! Can you provide full thread dumps from all nodes during max load? -- Ilya Kasnacheev пн, 4 мар. 2019 г. в 10:01, c c : More information. The cache is partitioned and full sync. c c 于2019年3月4日周一 下午2:54写道： HI, We are working on ignite 2.7.0. We just put entity into ignite cache with transaction and backup(2) enabled. We can get 6000 TPS with 3 server node. Then we test on 5 server nodes. But tps does not increase. We operate ignite by client server node embbed in application. Except for "publicThreadPoolSize" and "systemThreadPoolSize" other configurations left unchanged. What problem is it ? thanks 1.txt Description: Binary data
Re: Access a cache loaded by DataStreamer with SQL
Hello!
You can see at this page:
https://apacheignite-sql.readme.io/docs/sql-and-key-value-usage
And then substitite cache.put() with addData() and cache name will be
SQL_PUBLIC_{table name in caps}
There are not many examples since this is being discouraged in favor of SET
STREAMING ON, actually:
https://apacheignite-sql.readme.io/docs/set
Regards,
--
Ilya Kasnacheev
пт, 1 мар. 2019 г. в 22:48, Mike Needham :
> I have looked at the documentation and the code samples and nothing is
> doing what I am trying to do. I want to be able to use the datastreamer to
> load 3 or 4 TABLES in a cache for an application that we use. If I create
> the tables using a create table syntax how do attach a datastreamer to the
> different caches if the cache name is PUBLIC for all of them?
>
> On Thu, Feb 28, 2019 at 8:13 AM Ilya Kasnacheev
> wrote:
>
>> Hello!
>>
>> I have linked the documentation page, there are also some code examples
>> in distribution.
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> чт, 28 февр. 2019 г. в 17:10, Mike Needham :
>>
>>> Is there any examples that show the steps to do this correctly? I
>>> stumbled upon this but have no idea if it is the best way to do this
>>>
>>> On Thu, Feb 28, 2019 at 6:27 AM Ilya Kasnacheev <
>>> ilya.kasnach...@gmail.com> wrote:
>>>
Hello!
There's no restriction on cache name but setting it up for the first
time may be tricky indeed.
Regards,
--
Ilya Kasnacheev
ср, 27 февр. 2019 г. в 19:48, needbrew99 :
> OK, was able to get it working. Apparently the cache name has to be
> PUBLIC
> and it will create a table based on the object definition that I
> have.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
>>>
>>> --
>>> *Some days it just not worth chewing through the restraints*
>>>
>>
>
> --
> *Some days it just not worth chewing through the restraints*
>
Re: Failed to load bean in application context [beanName=cassandraAdminDataSource, igniteConfig=org.springframework.context.support.GenericApplicationContext
Hello! I am guessing that configured caches contain reference to Cassandra data store, for which you indeed do not have required Spring bean in your Spring context. Since you can't change cache configuration once it is there, the recommendation is to add dummy Spring bean with such name and proper type, even if it is not connected anywhere. The alternative is complete data loss, at least on affected caches. Regards, -- Ilya Kasnacheev пн, 4 мар. 2019 г. в 02:33, Max Barrios : > I am getting the above error when I attempt to activate a baseline Ignite > cluster ( > > I have stopped and started the nodes in the cluster. I have attempted to > deactivate the cluster and reactivate it. > > /home/ubuntu/apache-ignite-fabric-2.6.0-bin$ ./bin/control.sh --baseline > Control utility [ver. 2.6.0#20180710-sha1:669feacc] > 2018 Copyright(C) Apache Software Foundation > User: ubuntu > > Cluster state: inactive > Current topology version: 1 > > Baseline nodes: > ConsistentID=1de6f1ea-8991-4dff-8f8f-7ded9960bc33, STATE=ONLINE > ConsistentID=71893185-c471-40bd-8516-764dad910719, STATE=ONLINE > ConsistentID=7e56ac72-a2ce-4bb4-885c-91e1b0230d79, STATE=ONLINE > > Number of baseline nodes: 3 > > Other nodes not found. > /home/ubuntu/apache-ignite-fabric-2.6.0-bin$ ./bin/control.sh --state > Control utility [ver. 2.6.0#20180710-sha1:669feacc] > 2018 Copyright(C) Apache Software Foundation > User: ubuntu > > Cluster is inactive > /home/ubuntu/apache-ignite-fabric-2.6.0-bin$ ./bin/control.sh --deactivate > Control utility [ver. 2.6.0#20180710-sha1:669feacc] > 2018 Copyright(C) Apache Software Foundation > User: ubuntu > > Warning: the command will deactivate a cluster. > Press 'y' to continue . . . y > Cluster deactivated > /home/ubuntu/apache-ignite-fabric-2.6.0-bin$ ./bin/control.sh --activate > Control utility [ver. 2.6.0#20180710-sha1:669feacc] > 2018 Copyright(C) Apache Software Foundation > User: ubuntu > > Failed to activate cluster. > Error: Failed to activate cluster > suppressed: > Failed to load bean in application context > [beanName=cassandraAdminDataSource, > igniteConfig=org.springframework.context.support.GenericApplicationContext@55f3ddb1: > startup date [Sun Mar 03 23:23:06 GMT 2019]; root of context hierarchy] > > > Nothing works. I cannot get activate the existing baseline topology. I > cannot get rid of the baseline topology to create another one. And > activation only throws the exception and I haven't found any solution to > fix it. > > How do I: > 1) Address this exception? > 2) Force a drop of the current baseline so I can recreate the topology? >
Re: TPS does not increase even though new server nodes added
Hello! Can you provide full thread dumps from all nodes during max load? -- Ilya Kasnacheev пн, 4 мар. 2019 г. в 10:01, c c : > More information. The cache is partitioned and full sync. > > c c 于2019年3月4日周一 下午2:54写道： > >> HI, >> We are working on ignite 2.7.0. We just put entity into ignite cache >> with transaction and backup(2) enabled. We can get 6000 TPS with 3 server >> node. Then we test on 5 server nodes. But tps does not increase. We operate >> ignite by client server node embbed in application. Except for >> "publicThreadPoolSize" and "systemThreadPoolSize" other configurations left >> unchanged. What problem is it ? >>thanks >> >
Re: TPS does not increase even though new server nodes added
More information. The cache is partitioned and full sync. c c 于2019年3月4日周一 下午2:54写道： > HI, > We are working on ignite 2.7.0. We just put entity into ignite cache > with transaction and backup(2) enabled. We can get 6000 TPS with 3 server > node. Then we test on 5 server nodes. But tps does not increase. We operate > ignite by client server node embbed in application. Except for > "publicThreadPoolSize" and "systemThreadPoolSize" other configurations left > unchanged. What problem is it ? >thanks >
TPS does not increase even though new server nodes added
HI, We are working on ignite 2.7.0. We just put entity into ignite cache with transaction and backup(2) enabled. We can get 6000 TPS with 3 server node. Then we test on 5 server nodes. But tps does not increase. We operate ignite by client server node embbed in application. Except for "publicThreadPoolSize" and "systemThreadPoolSize" other configurations left unchanged. What problem is it ? thanks
Ignite put/query takes more than 500ms occasionally
Hello Ignites - I have an ignite cluster with 8c16 configuration and SSD disk, sometimes the cache put/query operations may take more 500ms. Here is my cache configuration: https://github.com/RedBlackTreei/streamer And I dumped five thread logs when timeout (>500ms) occurred, You can get it in the attachments. Looking forward to your replies.<>
Ignite put/query takes more than 500ms occasionally
Hello Ignites - I have an ignite cluster with 8c16 configuration and SSD disk, sometimes the cache put/query operations may take more 500ms. Here is my cache configuration: https://github.com/RedBlackTreei/streamer And I dumped five thread logs when timeout (>500ms) occurred, You can get it in the attachments. Looking forward to your replies.<>
Failed to load bean in application context [beanName=cassandraAdminDataSource, igniteConfig=org.springframework.context.support.GenericApplicationContext
I am getting the above error when I attempt to activate a baseline Ignite cluster ( I have stopped and started the nodes in the cluster. I have attempted to deactivate the cluster and reactivate it. /home/ubuntu/apache-ignite-fabric-2.6.0-bin$ ./bin/control.sh --baseline Control utility [ver. 2.6.0#20180710-sha1:669feacc] 2018 Copyright(C) Apache Software Foundation User: ubuntu Cluster state: inactive Current topology version: 1 Baseline nodes: ConsistentID=1de6f1ea-8991-4dff-8f8f-7ded9960bc33, STATE=ONLINE ConsistentID=71893185-c471-40bd-8516-764dad910719, STATE=ONLINE ConsistentID=7e56ac72-a2ce-4bb4-885c-91e1b0230d79, STATE=ONLINE Number of baseline nodes: 3 Other nodes not found. /home/ubuntu/apache-ignite-fabric-2.6.0-bin$ ./bin/control.sh --state Control utility [ver. 2.6.0#20180710-sha1:669feacc] 2018 Copyright(C) Apache Software Foundation User: ubuntu Cluster is inactive /home/ubuntu/apache-ignite-fabric-2.6.0-bin$ ./bin/control.sh --deactivate Control utility [ver. 2.6.0#20180710-sha1:669feacc] 2018 Copyright(C) Apache Software Foundation User: ubuntu Warning: the command will deactivate a cluster. Press 'y' to continue . . . y Cluster deactivated /home/ubuntu/apache-ignite-fabric-2.6.0-bin$ ./bin/control.sh --activate Control utility [ver. 2.6.0#20180710-sha1:669feacc] 2018 Copyright(C) Apache Software Foundation User: ubuntu Failed to activate cluster. Error: Failed to activate cluster suppressed: Failed to load bean in application context [beanName=cassandraAdminDataSource, igniteConfig=org.springframework.context.support.GenericApplicationContext@55f3ddb1: startup date [Sun Mar 03 23:23:06 GMT 2019]; root of context hierarchy] Nothing works. I cannot get activate the existing baseline topology. I cannot get rid of the baseline topology to create another one. And activation only throws the exception and I haven't found any solution to fix it. How do I: 1) Address this exception? 2) Force a drop of the current baseline so I can recreate the topology?
