Re: [RESULT] Move usergrid repos to gitbox.apache.org
To close this out, the migration to gitbox is completed. Committers: You can update your Apache git remote URLs to https://gitbox.apache.org/repos/asf/usergrid.git (previously https://git-wip-us.apache.org/repos/asf/usergrid.git) Also, to take advantage of working directly from Github, your Github account will need to be linked to Apache. Visit https://gitbox.apache.org/setup. Thanks. -Michael On Sun, Jan 6, 2019 at 4:03 PM Michael Russo wrote: > The vote has passed and I've opened > https://issues.apache.org/jira/browse/INFRA-17568. > > On Thu, Jan 3, 2019 at 11:10 AM Rod Simpson wrote: > >> +1 >> >> On Thu, Jan 3, 2019, 11:19 AM Dave > >> > +1 >> > >> > Finally, Usergrid committers will be able to merge GitHub PRs with the >> > click of a button. >> > >> > On Thu, Jan 3, 2019 at 12:07 PM Michael Russo >> > wrote: >> > >> > > Hi All, >> > > >> > > Given the recent notices from Apache Infra team, I'm proposing that >> we go >> > > ahead and migrate all of the usergrid repos to gitbox.apache.org >> before >> > > the >> > > forced migration. This will not change community >> contribution/interaction >> > > via Github. See the notice email >> > > < >> > > >> > >> https://lists.apache.org/thread.html/b9ab62075cc7fcb8ee0c2c0b1d4c39f2ae5918bd4c041dc9bf8350ef@%3Cdev.usergrid.apache.org%3E >> > > >for >> > > more details. >> > > >> > > Please vote on the early migration. >> > > >> > > The vote will be open for 72 hours. >> > > [ ] +1 Go ahead with the move to gitbox >> > > [ ] +0 no opinion >> > > [ ] -1 Do not migrate early to gitbox because ... >> > > >> > > Thanks. >> > > -Michael >> > > >> > >> >
[jira] [Resolved] (USERGRID-1356) Make entity fetcher threads configurable for Export
[ https://issues.apache.org/jira/browse/USERGRID-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keyur Karnik resolved USERGRID-1356. Resolution: Fixed Fix Version/s: 2.2.0 https://github.com/apache/usergrid/pull/620 > Make entity fetcher threads configurable for Export > --- > > Key: USERGRID-1356 > URL: https://issues.apache.org/jira/browse/USERGRID-1356 > Project: Usergrid > Issue Type: Improvement > Components: Stack >Affects Versions: 2.2.0 >Reporter: Keyur Karnik >Assignee: Keyur Karnik >Priority: Minor > Fix For: 2.2.0 > > > The new export tool first fetches all Entity ids and as it fetches them, it > starts parallel exports in batches of 1000. > Depending on the data in each entity and the number and size of assets and > members (connections etc), this process can take a long time. But as we can > safely process it in parallel, we can increase the number of threads to make > it faster (keeping resource utilization in mind). > To do this, we need to add configs to set and tune fetcher thread counts. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (USERGRID-1356) Make entity fetcher threads configurable for Export
[ https://issues.apache.org/jira/browse/USERGRID-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755517#comment-16755517 ] Keyur Karnik commented on USERGRID-1356: Fixed here : https://github.com/apache/usergrid/pull/620 > Make entity fetcher threads configurable for Export > --- > > Key: USERGRID-1356 > URL: https://issues.apache.org/jira/browse/USERGRID-1356 > Project: Usergrid > Issue Type: Improvement > Components: Stack >Affects Versions: 2.2.0 >Reporter: Keyur Karnik >Assignee: Keyur Karnik >Priority: Minor > > The new export tool first fetches all Entity ids and as it fetches them, it > starts parallel exports in batches of 1000. > Depending on the data in each entity and the number and size of assets and > members (connections etc), this process can take a long time. But as we can > safely process it in parallel, we can increase the number of threads to make > it faster (keeping resource utilization in mind). > To do this, we need to add configs to set and tune fetcher thread counts. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (USERGRID-1356) Make entity fetcher threads configurable for Export
Keyur Karnik created USERGRID-1356: -- Summary: Make entity fetcher threads configurable for Export Key: USERGRID-1356 URL: https://issues.apache.org/jira/browse/USERGRID-1356 Project: Usergrid Issue Type: Improvement Components: Stack Affects Versions: 2.2.0 Reporter: Keyur Karnik Assignee: Keyur Karnik The new export tool first fetches all Entity ids and as it fetches them, it starts parallel exports in batches of 1000. Depending on the data in each entity and the number and size of assets and members (connections etc), this process can take a long time. But as we can safely process it in parallel, we can increase the number of threads to make it faster (keeping resource utilization in mind). To do this, we need to add configs to set and tune fetcher thread counts. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (USERGRID-1355) Dissociate akka based Unique Value checks across regions for a multi region distributed cluster using Qakka
Keyur Karnik created USERGRID-1355: -- Summary: Dissociate akka based Unique Value checks across regions for a multi region distributed cluster using Qakka Key: USERGRID-1355 URL: https://issues.apache.org/jira/browse/USERGRID-1355 Project: Usergrid Issue Type: Improvement Components: Stack Affects Versions: 2.2.0 Reporter: Keyur Karnik Assignee: Keyur Karnik Fix For: 2.2.0 To setup a Qakka cluster across multiple regions, we need to enable the following settings usergrid.cluster.enabled usergrid.cluster.seeds (add multiple regions and seed ips) elasticsearch.queue_impl=DISTRIBUTED Doing so sets up the Akka cluster across region but it has some side effects collection.uniquevalues.usecluster setting which is true by default comes into play, so all unique value checks start using Akka. To compound it, if Akka is multi region, it coordinates with all Akka remote clusters as well. This may not be intended and there is no way to stop this (just the remote checks) To resolve this : Set the collection.uniquevalues.usecluster to false by default Create a new config that can restrict UniqueValue checks and Akka chatter to the local cluster only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (USERGRID-1354) Akka cluster does not work for more than 2 regions
[ https://issues.apache.org/jira/browse/USERGRID-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keyur Karnik updated USERGRID-1354: --- Comment: was deleted (was: Fixed in PR 619 https://github.com/apache/usergrid/pull/619) > Akka cluster does not work for more than 2 regions > -- > > Key: USERGRID-1354 > URL: https://issues.apache.org/jira/browse/USERGRID-1354 > Project: Usergrid > Issue Type: Bug > Components: Stack >Affects Versions: 2.2.0 >Reporter: Keyur Karnik >Assignee: Keyur Karnik >Priority: Major > Fix For: 2.2.0 > > > When UG is started with Akka enabled and more than 2 DCs are provided in the > UG seeds, the cluster startup fails with > Error starting Akka akka.actor.InvalidActorNameException: actor name [client] > is not unique! > Multiple regions are set by setting this config > usergrid.cluster.seeds=dc1:ip1, dc1:ip2, dc2:ip1, dc2:ip2, dc3:ip1, dc3:ip2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (USERGRID-1354) Akka cluster does not work for more than 2 regions
Keyur Karnik created USERGRID-1354: -- Summary: Akka cluster does not work for more than 2 regions Key: USERGRID-1354 URL: https://issues.apache.org/jira/browse/USERGRID-1354 Project: Usergrid Issue Type: Bug Components: Stack Affects Versions: 2.2.0 Reporter: Keyur Karnik Assignee: Keyur Karnik When UG is started with Akka enabled and more than 2 DCs are provided in the UG seeds, the cluster startup fails with Error starting Akka akka.actor.InvalidActorNameException: actor name [client] is not unique! Multiple regions are set by setting this config usergrid.cluster.seeds=dc1:ip1, dc1:ip2, dc2:ip1, dc2:ip2, dc3:ip1, dc3:ip2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
