Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 09:40
    zhangyiqiu starred exceptionless/Exceptionless
  • 07:45
  • 05:47
    ejsmith edited #471
  • 05:46
    ejsmith opened #471
  • 05:46

    ejsmith on strip-large-data

    Strip large data values out of … (compare)

  • Dec 11 19:54
    niemyjski synchronize #452
  • Dec 11 19:54

    niemyjski on elastic7

    Decrease batch size (compare)

  • Dec 11 14:51
    niemyjski synchronize #452
  • Dec 11 14:51

    niemyjski on elastic7

    Reset the alias cache before ru… (compare)

  • Dec 11 04:03

    ejsmith on mappings-refactor

    (compare)

  • Dec 11 04:02
    ejsmith synchronize #452
  • Dec 11 04:02

    ejsmith on elastic7

    Change a bunch of index field s… Updated dependencies. Revert to 2201-pre and 6 more (compare)

  • Dec 11 04:02
    ejsmith closed #470
  • Dec 11 04:02
    ejsmith edited #470
  • Dec 11 03:59
    ejsmith opened #470
  • Dec 11 03:14

    niemyjski on mappings-refactor

    Updated to latest foundatio (compare)

  • Dec 11 02:59

    niemyjski on mappings-refactor

    Tweaked the event index mapping… (compare)

  • Dec 11 01:53

    ejsmith on mappings-refactor

    Update cache client list method… (compare)

  • Dec 11 01:19

    ejsmith on mappings-refactor

    More index work (compare)

  • Dec 10 13:26
    niemyjski commented #468
Blake Niemyjski
@niemyjski
The thing is open the job.exe.config and set the redis connection string
I just thought about that
because you need to queue the migrations to someplace (default is in memory)
and that doesn't really work when you have multiple processes
@woehrl01 we just added the -s flag in the latest nightly hehe
Lukas Wöhrl
@woehrl01
I just executed those, but still no additional exceptions :-/
Blake Niemyjski
@niemyjski
you'll need to configure redis
otherwise the queue event migrations job is just going to queue things to nothing
(in memory queue)
Did the stacks show up in your elastic search instance
Lukas Wöhrl
@woehrl01
no, the stacks are not showing up
I just renabled redis but still no exceptionions
so. I changed job.exe.config to the same values aus web.config (mongodb/redis/elastic) and I reexecuted the statements above for StackMigrationJob, QueueEventMigrationsJob and EventMigrationJob
but, the old exceptions are still not showing up
any further suggestions?
Lukas Wöhrl
@woehrl01
I just enabled, the INFO logging level. and it prints the following: The daterange looks a little bit off?
2015-06-11 17:14:30.9660|INFO|JobRunner|Starting job type "EventMigrationJob" on machine "VM9-DEV"...
2015-06-11 17:14:31.1126|WARN|Bootstrapper|StatsD Metrics is NOT enabled.
2015-06-11 17:14:31.2572|WARN|Bootstrapper|Azure Storage is NOT enabled.
2015-06-11 17:14:32.8286|INFO|MigrationJobBase|Public IP: 79.255.159.7
2015-06-11 17:14:32.8579|INFO|EventMigrationJob|Processing event migration jobs
for date range: 2014-07-31T00:00:00.0000000+00:00-2014-07-31T12:00:00.0000000+00:00
2015-06-11 17:14:33.4149|INFO|EventMigrationJob|Finished processing event migration jobs for date range: 2014-07-31T00:00:00.0000000+00:00-2014-07-31T12:00:00.0000000+00:00
Blake Niemyjski
@niemyjski
Yeah that is good it's doing 12 hour day increments
that looks good
anything in the log for migrating stacks
If you want I could jump on a remote meeting for a few minutes and help take a look
Lukas Wöhrl
@woehrl01
yeah, I cleared redis and did all of this again, and with info enabled I get:
2015-06-11 17:21:57.3987|INFO|StackMigrationJob|Migrating stacks 8.000 total 2.711/s...
2015-06-11 17:21:57.4192|INFO|StackMigrationJob|Migrating stacks 8.050 total 2.711/s... etc
looks good so far, except that it's not showing :D
Blake Niemyjski
@niemyjski
we'll what are you using to look at your elastic search content
elastic hq plugin?
Lukas Wöhrl
@woehrl01
I have currently nothing installed to look at the content
just installed elasticsearch for exceptionless
go there and then enter in your connection string for elastic
as shown and then connect
it will show you all the indexs / records
Lukas Wöhrl
@woehrl01
looks, good, I have >8000 stacks-v1 about the same count like in mongodb
Blake Niemyjski
@niemyjski
ok
so looks like those were migrated
now just need to migrate events
how many errors do you have?
Lukas Wöhrl
@woehrl01
none, inside of elastic
Blake Niemyjski
@niemyjski
yes but in mongo
Lukas Wöhrl
@woehrl01
about 46k
Blake Niemyjski
@niemyjski
ok
that should be a pretty quick migration
you should just have to queue them
and them run the migration job
Lukas Wöhrl
@woehrl01
it is just queueing from today
Blake Niemyjski
@niemyjski
2015-06-11 17:14:32.8579|INFO|EventMigrationJob|Processing event migration jobs
for date range: 2014-07-31T00:00:00.0000000+00:00-2014-07-31T12:00:00.0000000+00:00
Lukas Wöhrl
@woehrl01
aaaaah, i see , i have to run the last one with -c
Blake Niemyjski
@niemyjski
it looks like it started queueing from 11m ago
ahh yeah