Closed
Bug 657610
Opened 14 years ago
Closed 14 years ago
[prod] ISE: IntegrityError: (1062, "Duplicate entry '' for key 'markup_mark_reference_uniq'")
Categories
(Websites Graveyard :: markup.mozilla.org, defect)
Websites Graveyard
markup.mozilla.org
Tracking
(Not tracked)
VERIFIED
FIXED
1.0
People
(Reporter: mbrandt, Assigned: wenzel)
Details
/requests/save_mark
Traceback (most recent call last):
File "/data/www/python/markup.mozilla.org/markup/ffdemo/vendor/src/django/django/core/handlers/base.py", line 100, in get_response
response = callback(request, *callback_args, **callback_kwargs)
File "/data/www/python/markup.mozilla.org/markup/ffdemo/vendor/src/django/django/views/decorators/http.py", line 37, in inner
return func(request, *args, **kwargs)
File "/data/www/python/markup.mozilla.org/markup/ffdemo/markup/requests.py", line 123, in save_mark
new_mark_reference = common.save_new_mark_with_data(mark_data, request.META['REMOTE_ADDR'])
File "/data/www/python/markup.mozilla.org/markup/ffdemo/../ffdemo/markup/common.py", line 69, in save_new_mark_with_data
new_mark = Mark.objects.create()
File "/data/www/python/markup.mozilla.org/markup/ffdemo/vendor/src/django/django/db/models/manager.py", line 138, in create
return self.get_query_set().create(**kwargs)
File "/data/www/python/markup.mozilla.org/markup/ffdemo/vendor/src/django/django/db/models/query.py", line 352, in create
obj.save(force_insert=True, using=self.db)
File "/data/www/python/markup.mozilla.org/markup/ffdemo/vendor/src/django/django/db/models/base.py", line 434, in save
self.save_base(using=using, force_insert=force_insert, force_update=force_update)
File "/data/www/python/markup.mozilla.org/markup/ffdemo/vendor/src/django/django/db/models/base.py", line 527, in save_base
result = manager._insert(values, return_id=update_pk, using=using)
File "/data/www/python/markup.mozilla.org/markup/ffdemo/vendor/src/django/django/db/models/manager.py", line 195, in _insert
return insert_query(self.model, values, **kwargs)
File "/data/www/python/markup.mozilla.org/markup/ffdemo/vendor/src/django/django/db/models/query.py", line 1479, in insert_query
return query.get_compiler(using=using).execute_sql(return_id)
File "/data/www/python/markup.mozilla.org/markup/ffdemo/vendor/src/django/django/db/models/sql/compiler.py", line 783, in execute_sql
cursor = super(SQLInsertCompiler, self).execute_sql(None)
File "/data/www/python/markup.mozilla.org/markup/ffdemo/vendor/src/django/django/db/models/sql/compiler.py", line 727, in execute_sql
cursor.execute(sql, params)
File "/data/www/python/markup.mozilla.org/markup/ffdemo/vendor/src/django/django/db/backends/mysql/base.py", line 86, in execute
return self.cursor.execute(query, args)
File "/usr/lib/python2.6/site-packages/MySQLdb/cursors.py", line 173, in execute
self.errorhandler(self, exc, value)
File "/usr/lib/python2.6/site-packages/MySQLdb/connections.py", line 36, in defaulterrorhandler
raise errorclass, errorvalue
IntegrityError: (1062, "Duplicate entry '' for key 'markup_mark_reference_uniq'")
| Reporter | ||
Updated•14 years ago
|
Severity: normal → blocker
| Reporter | ||
Updated•14 years ago
|
Target Milestone: --- → 1.0
| Assignee | ||
Comment 1•14 years ago
|
||
Reason for this traceback fixed here:
https://github.com/mozilla/markup/commit/f9fd7d6
The underlying performance problem persists: bug 657805.
Assignee: nobody → fwenzel
Status: NEW → RESOLVED
Closed: 14 years ago
OS: Mac OS X → All
Hardware: x86 → All
Resolution: --- → FIXED
| Reporter | ||
Comment 2•14 years ago
|
||
I'm want to wait for the results of our jmeter load testing before closing this. This was originally uncovered via our load tests.
| Reporter | ||
Comment 3•14 years ago
|
||
QA verified... 15 threaded processes each submitted 10 complex marks for a total of 150 marks
Status: RESOLVED → VERIFIED
| Assignee | ||
Comment 4•14 years ago
|
||
Right on, Matt! Thanks for running that test again. Looks like we got the save() step to be quite robust now.
| Reporter | ||
Comment 5•14 years ago
|
||
Yes! ubber::woot
Updated•4 years ago
|
Product: Websites → Websites Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•